Displaying time-varying internet based data using application media packages

ABSTRACT

A software component for accessing and displaying time-varying Internet content includes a definition for rendering a graphical user interface and a URL pointing to the time-varying Internet content to be downloaded and presented within said user interface. A component provider may create displays of Internet content which vary as a function of the varying of the time-varying Internet content. In one example, the graphical user interface includes an image, and the image varies in order to illustrate the varying of the time-varying data.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of and incorporates byreference U.S. Non-Provisional patent application Ser. No. 09/558,925,filed Apr. 26, 2000, now U.S. Pat. No. 7,660,868, which claims priorityfrom and incorporates by reference U.S. Provisional Application Ser.Nos. 60/131,083, filed Apr. 26, 1999, 60/131,114, filed Apr. 26, 1999,60/131,115, filed Apr. 26, 1999, 60/176,687, filed Jan. 18, 2000, and60/176,699, filed Jan. 18, 2000. The present application claims priorityto U.S. Non-Provisional patent application Ser. No. 09/558,925, filedApr. 26, 2000, now U.S. Pat. No. 7,660,868, and each of theaforementioned applications to which it claims priority.

The present application is also related to and incorporates by referencethe following U.S. patent applications: Non-Provisional application Ser.No. 09/558,922, filed Apr. 26, 2000, now U.S. Pat. No. 7,756,967;Non-Provisional application Ser. No. 09/558,923, filed Apr. 26, 2000;Non-Provisional application Ser. No. 09/558,924, filed Apr. 26, 2000,now U.S. Pat. No. 7,356,569; Non-Provisional application Ser. No.11/932,286, filed Oct. 31, 2007 titled “Component For Accessing AndDisplaying Internet Content”; Non-Provisional application Ser. No.11/932,286, filed Oct. 31, 2007, titled “Server Including Components ForAccessing And Displaying Internet Content And For Providing Same To AClient”; Non-Provisional Application Ser. No. 11/932,392, filed Oct. 31,2007, titled “Method For Accessing And Displaying Internet Content”;Non-Provisional application Ser. No. 11/932,427, filed Oct. 31, 2007,titled “Component For Coordinating The Accessing And Rendering Of AnApplication Media Package”; Non-Provisional application Ser. No.11/932,456, filed Oct. 31, 2007, titled “Tracking and Tracing UserActivity with Application Media Packages”; Non-Provisional applicationSer. No. 11/932,585, filed Oct. 31, 2007, titled “System and Methods forCreating and Authoring Internet Content using Application MediaPackages”; Non-Provisional application Ser. No. 11/932,630, filed Oct.31, 2007, titled “Methods of Obtaining Application Media Packages”;Non-Provisional application Ser. No. 11/932,663, filed Oct. 31, 2007,titled “Indexing, Sorting, and Categorizing Dots”; Non-Provisionalapplication Ser. No. 11/932,692, filed Oct. 31, 2007, titled “System andMethods of Messaging between Application Media Packages; and,Non-Provisional application Ser. No. 11/932,763, filed Oct. 31, 2007,titled “Component For Accessing And Displaying Internet Content InAssociation With a Web Browser Application”.

BACKGROUND OF THE INVENTION

A user operating a client computer typically accesses the Internet byusing a viewer application, such as a browser to view web contentprovided at a destination address, typically a web page. In thiscontext, web content and web applications are designed to fill theentire web page. It is known to divide the web content into differentregions of a single web page. For example, personalized web pages can bespecified, such that a user views a variety of content sources in asingle page, such as stock information, weather information, and sportsinformation, which is aggregated at the server that delivers the webpage to the user, who then views the aggregated content in a single webpage. Observe that even when disparate content is aggregated, in thismanner, it is reassembled into a full web page and is served through afull-screen browser. Web content and application developers thereforehave limited control over the user experience: content is typicallytrapped within the frame of the browser. A developer's only alternativeto engaging a user page-by-page in a browser is to develop, distribute,and support custom client software. In the Web browser scenario, it isthe content provider, not the user that aggregates the information thatis viewed by the user. Thus, the user is not in a position to separatelyaggregate the content at a client computer, instead the user isconstrained to view the content that has been delivered in the mannerprovided by the server computer hosting the web page. There is a growingdesire for individual users to fully control the aggregation andpresentation of content and web applications that appears on a clientcomputer.

A user who wishes to view multiple web pages or applications can openmultiple instances of a browser. However, the user will not be able toview each “full-screen” page at the same time. Instead, the user mustadjust the windows corresponding to each browser instance and view onlypart of each page. The information appearing in each browser is notdesigned for viewing in this manner. Thus, the user cannot create anoptimized display of content from multiple sources.

Currently, content providers and end users have limited tools to alterthe browser in which content appears. That is, the controls associatedwith a browser are not fully configurable. Thus, the vendor of a browseris in a position to brand the browser and regulate the controlsassociated with the browser. There is a growing desire for contentproviders to not only fill a browser with their content, but to alsofully brand and control the frame in which the content appears. Further,in some instances, content providers desire to limit the controlsassociated with a browser or viewer, so that a user is more inclined toview a single set of content, for example, by having limited access topreviously viewed content.

At the present time, it is relatively difficult to trace the contentviewing activity of a client computer. In other words, it is difficultto identify the type of content that a particular user of a clientcomputer favors. Consequently, there are limited tools 25 available toprovide a user with tailored information that would be of particularinterest to the user.

In view of the foregoing, there is a need in the art to provide atechnique for accessing multiple instances of distributable computerreadable media in their entirety simultaneously, where these instancesare typically smaller than the full pages used in 30 current web pagesand web applications. There is a further need for providing the userwith flexibility in selecting, collecting, relating and viewing suchcomputer readable media, and for giving the media provider flexibilityin directing media to a specific user and controlling the framework inwhich media is presented. Finally, there is a need to gather moreaccurate information regarding the type of content that a user enjoys,so that the user can be automatically provided with this content.

SUMMARY OF THE INVENTION

The invention includes a method of presenting distributable computerreadable media to a user in response to a user request. The methodcomprises the steps of identifying a definition of a NetworkedInformation Monitor (NIM). A NIM frame is defined for the NIM using thedefinition. Content is then retrieved for the NIM. Then, the content isplaced in a NIM viewer defined by the frame.

The invention also includes a method of altering a Networked InformationMonitor (NIM). The method includes the step of receiving a message at aNIM. The message specifies a configurable feature of the NUM. The NIM isaltered in accordance with the configurable feature of the message.

The apparatus of the invention includes a computer readable memory todirect a computer to function in a specific manner. The computerreadable memory includes a first executable module to identify adefinition of a Networked Information Monitor (NIM). A second executablemodule defines a NIM frame for the NIM using the definition. A thirdexecutable module retrieves content for the NIM. A fourth executablemodule places the content in a NUM viewer defined by the frame.

The apparatus of the invention further includes a computer readablememory with a first executable module to receive a Networked InformationMonitor (NIM) message. The NIM message specifies a configurable featureof a NIM. A second executable module alters the NIM in accordance withthe configurable feature of the NIM message.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system for processing distributable computerreadable media in accordance with one embodiment of the presentinvention;

FIG. 2 shows exemplary processing steps used to initiate an instance ofa home networked information monitor (NIM) using the apparatus of FIG.1;

FIG. 3A illustrates a screen logo in accordance with one embodiment ofthe present invention;

FIG. 3B illustrates a login construct in accordance with one embodimentof the present invention;

FIG. 4 illustrates a set of visual manifestations corresponding to acollection of NIMs, including a home NIM;

FIG. 5 illustrates a visual manifestation of a home NIM as well as avisual manifestation of a reference NIM that references additional NIMs;

FIG. 6 illustrates how a NIM, referenced by the reference NIM of FIG. 5,is added to a processed user profile in response to a designatedkeyboard entry sequence or mouse click;

FIG. 7 illustrates how a NIM is shared with other users in accordancewith an embodiment of the present invention;

FIGS. 8A and 8B illustrate screen panels that facilitate the collectionof the description of a set of designated NIMs into a pack;

FIG. 9A illustrates how the relative position of visual manifestationsthat correspond to NIMs remains fixed when the visual manifestations arewithin a predetermined distance of each other;

FIG. 9B illustrates a representative pack in accordance with the present20 invention;

FIGS. 10A, 10B and 10C illustrate how a set of visual manifestationscorresponding to a collection of NIMs is aligned against a boundary whena user selects the visual manifestations and pushes them against theboundary;

FIG. 11 is a flow chart of the steps taken by a client to give a useraccess to a NIM where the user “collects” the NIM, in accordance withone embodiment of the invention;

FIG. 12 is a flow chart of the steps taken by a client to present a NIMto a user, where the NIM has been “collected” previously by the user, inaccordance with one embodiment of the invention;

FIG. 13 illustrates a data structure for a NIM definition, stored in theNIM application server's template database or user profile database;

FIG. 14 illustrates NMA message routing between NIMs and the messageinterface in the client parser application;

FIG. 15 is a diagrammatic illustration of an embodiment of a NIMManagement Module utilized in accordance with an embodiment of theinvention;

FIG. 16 is a diagrammatic illustration of an embodiment of the NIMTemplates database utilized in accordance with an embodiment of theinvention;

FIG. 17 is an illustration of a main NIMIndex Web page used inaccordance with an embodiment of the invention;

FIG. 18 is an illustration of a single NIMIndex category used inaccordance with an embodiment of the invention;

FIG. 19 is an illustration of a full description of NIM content providedin accordance with an embodiment of the invention;

FIG. 20 is an illustration of a Web page displayed to the user once theuser has clicked to collect the NIM;

FIG. 21 is an illustration of the main home NIM graphical user interfaceused in accordance with an embodiment of the invention;

FIG. 22 is an illustration of a “Get New NIM” graphical user interfacethat may be used in accordance with an embodiment of the invention;

FIG. 23 is an illustration of a “More NIMs” graphical user interfacerepresentative of an embodiment of the invention;

FIG. 24 is a diagrammatic illustration of the ShareLink database used inaccordance with an embodiment of the invention;

FIG. 25 is an illustration of a Share NIM's graphical user interfaceaccording to an embodiment of the invention;

FIG. 26 is an illustration of the main DevZone Web page utilized inaccordance with an embodiment of the invention;

FIG. 27 is a partial view of a NIM modification web page utilized inaccordance with an embodiment of the invention;

FIGS. 28A to 28D are graphical user interfaces of development NIMs(DevNIMs) utilized in accordance with an embodiment of the invention;

FIGS. 29A and 29B are illustrations of Administrative Zone (AdminZone)Web pages utilized in accordance with an embodiment of the invention;

FIGS. 30A and 30B are also illustrations of Administrative Zone(AdminZone) Web pages utilized in accordance with an embodiment of theinvention;

FIGS. 31A and 31B are further illustrations of Administrative Zone(AdminZone) Web pages utilized in accordance with an embodiment of theinvention;

FIG. 32 illustrates an embodiment of an event log that may be used inaccordance with an embodiment of the invention;

FIG. 33 illustrates the tracking of events in an event log module inaccordance with an embodiment of the invention;

FIG. 34 illustrates a statistics database that may be used in accordancewith an embodiment of the invention;

FIG. 35 illustrates a statistical analysis module and a content analysismodule that may be used in accordance with an embodiment of theinvention;

FIG. 36 illustrates a content database that may be used in accordancewith an embodiment of the invention; and

FIG. 37 illustrates a user account database that may be used inaccordance with an embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention discloses a technology that is capable ofprocessing distributable computer readable media. Distributable computerreadable media includes, but is not limited to, standard web content,such as HTML, dHTML, images, imbedded ActiveX and Java applications,JavaScript, CSS, Pen scripts, Streaming Media, and/or Flash. The presentinvention is advantageous relative to prior art systems and methodsbecause it provides improved mechanisms for simultaneously interactingwith several independent sources of distributable computer readablemedia, collecting references to such media, and sharing such referenceswith other users. The ac disclosed technology is further advantageousbecause it provides improved systems and methods for on screenmanagement of distributable computer readable media.

In the system and method of the present invention, a user logs into aserver by providing a login identifier to a login construct. The loginidentifier is used by the server to obtain an unprocessed user profilethat corresponds to the user. The unprocessed user profile is processedby the server to generate a processed user profile. Advantageously, thisprocessing step allows for up-to-date refinement of the user profile.Up-to-date refinements include, for example, the addition ofadvertisements directed to the user based on one or more characteristicsin the user profile. The processed user profile is delivered to theclient computer associated with the user. The processed user profileincludes references to the networked information monitors (NIMs). Asused herein, the term networked information monitor or NIM refers to afully configurable frame with one or more controls; the frame throughwhich content is optionally presented. The fully configurable frameutilized in accordance with the invention stands in contrast to presentweb browsers, which are branded by the browser vendor and which havelimited means by which to alter the controls associated with thebrowser.

Attention is initially directed toward the home NIM of the invention,which coordinates the activities of all other NIMs that are accessed bya user. The home NIM facilitates much of the technology of the presentinvention, including the ability to simultaneously review multiplesources of distributable computer readable media as well as to packageand distribute such media.

FIG. 1 is a general illustration of a system in accordance with oneembodiment of the present invention. In FIG. 1, a network 10 is operatedin accordance with the present invention. Network 10 includes at leastone user or client computer 20, at least one server computer of class50, and optionally one or more server computers of class 82. Usercomputer 20 as well as server computers of class 20 50 and 82 are eachconnected by transmission channel 44, which is any wired or wirelesstransmission channel.

User computer 20 is any device that includes a Central Processing Unit(CPU) 24 connected to a random access memory 30, a network connection28, and one or more user input/output (“i/o”) devices 40 includingoutput means 42. Output means 42 is any device capable of communicatingwith a user and includes, for example, a video monitor, a liquid crystaldisplay, voice user interfaces, and/or integrated graphic means such asmini-displays present in web-phones. Typically, user computer 20includes a main non-volatile storage unit 22, preferably a hard diskdrive, for storing software and data. Further, user computer 20 includesone or more internal buses 26 for interconnecting the aforementionedelements. In a typical embodiment, memory 30 includes an operatingsystem 32 for managing files and programs associated with user computer20. In some embodiments, operating system 32 includes a registry 34 thathas one or more references to specified locations in system 10. Theexemplary memory 30 of FIG. 1 further includes a web browser 36 forviewing web content and a client parser application 38 for facilitatinglow level functionality, such as login and logout procedures, inaccordance with the present invention. In some embodiments, clientparser application 38 uses the one or more references in registry 34 toobtain a login construct from server 50. In various embodiments, inaccordance with the present invention, client parser application 38 runsin conjunction with one or more software modules, such as an event logmodule 98, which tracks user activity, a message interface module 106,which serves as a communication interface between the client parserapplication 38 and web server 58 and/or external web servers, a home NIM108, which references one or more NIMs 110, and a visual managementsystem 114 which regulates the characteristics of visual manifestationsof NIMs 108 and 110 when displayed on output device 42. Furthermore, insome embodiments, client parser application 38 runs in conjunction withinstances of web browser 36 as well as web server 58 as detailed below.

Server computer 50 includes standard server components, including anetwork connection device 46, a CPU 52, a main non-volatile storage unit54, and a random access memory 56. Further, server computer 50 includesone or more internal buses 48 for interconnecting the aforementionedelements. Memory 56 stores a set of computer programs, modules and datato implement the processing associated with the present invention.

The embodiment of memory 56 illustrated in FIG. 1 includes a web server58 for processing requests received from client computer 20. Web server58 has many components, including a variety of modules and datastructures to assist users that want to log into system 10. Namely,login module 60 handles an entry request from a client computer 20 andaccepts a login identifier that corresponds to a user from clientcomputer 20. Login constructor 62 generates a login construct inresponse to a call for a login construct and transfers the loginconstruct to client 20. Login constructor 62 dynamically generates loginconstructs using updated login NIM content 64. Login validation module66 works in conjunction with user profile database manager 100 toidentify an unprocessed user profile, which is associated with a userprovided login, in user profile database 76. If an unprocessed userprofile corresponding to the user provided login does not exist in userprofile database 76, login validation module 66 associates a newunprocessed user profile with the login identifier.

When an unprocessed user profile is identified by login validationmodule 66, it is processed by user profile processor module 68 toproduce a processed profile. It will be appreciated that the services ofuser profile processor module 68 are highly advantageous because theyallow for last minute user profile revisions. Such revisions include,for example, the addition or customization of NIMs referenced by theuser profile, and/or server redirect information that is a function ofcurrent server load in system 10. Importantly, the processed userprofile includes a reference to a home NIM. The home NIM is capable ofaccessing each of the NIMs that are represented in the processed userprofile. Memory 56 further includes delivery module 70, whichcoordinates the delivery of portions of the home NIM to the client basedon parameters specified in the processed user profile.

Once a user has successfully logged into system 10, request servermodule 72 handles requests for specified NIMs from client 20. When sucha request is received, request server module 72 routes the request to anaddress that corresponds to the specified NIM and transmits thespecified NIM to client 20. One class of specified networked informationhandled by request server module 72 is requests for NIMs. When such arequest is received, request server module 72 searches NIM templatesdatabase 74 for the specified NIM. NIM templates database 74 includes alarge number of NIM templates. Each NIM template defines thecharacteristics of a specific NIM, including fully configurable framecharacteristics, viewer and control characteristics, and NIM contentreferences.

The web server 58 illustrated in FIG. 1 further includes additionalmodules 102 to handle specialized features of the present invention. Forexample, one embodiment of the present invention provides a mechanismthat allows users to distribute NIMs to each other. In such embodiments,a special server module 102 provides instructions for storing the NIMs,which are to be distributed, in sharelink database 78. Advantageously,NIMs that are distributed to other users are customizable. A user can,for example, resize and position a particular NIM prior to sharing itwith another user. Indeed, it is possible, in such embodiments, for auser to arrange a series of NIMs in a unique arrangement and thendistribute the collection of NIMs in the designated NIMs in the designedarrangement. As an illustration, a user arranges a first NIM thatrepresents a scrolling stock ticker at the bottom of an output means,such as a computer screen, a second NIM that tracks the NASDAQ top tenmost heavily traded stocks in the upper left corner of the output means,and a third NIM that tracks headline news on the upper right hand cornerof the output means. Then, the user distributes the three NIMs in thiscustomized arrangement to other users. Observe that in this example auser of a client computer is aggregating separate sets of information indifferent NIMs. This stands in contrast to prior art approaches where aweb server running on a server computer aggregates information in asingle page.

System 10 is highly scalable and thus supports a large number of users.This scalability stems from the fact that the server 50 is deliveringthe definition associated with a NIM. The content displayed in the NIMmay be located on a separate computer.

Memory 56 provides a statistical analysis module 104 for tracking keyevents associated with users. This information is stored in statisticsdatabase 80. The information collected by statistical analysis module104 is used for a wide variety of purposes, including server loadoptimization and directed advertising, as discussed below. As describedbelow, the statistical information gathered in accordance with theinvention includes fully traced events defining the type of content andthe duration over which all content is viewed by a user. This type ofcomprehensive information is not available using present techniques.

Much of the distributable computer readable media that is available forprocessing is stored as content elements 94 on server 82. Server 82 is astandard web server that includes components such as a networkconnection device 88, a CPU 86, a main non-volatile storage unit 84, arandom access memory (RAM) 92, and one or more internal buses 90 forinterconnecting the aforementioned elements. RAM 92 includes some of thecontent elements 94 stored by server 82. Other content elements 94 arestored in storage unit 84. In some embodiments, a single web server 58is capable of directly accessing content elements 94 located on one ormore servers 82. In other embodiments, each server 82 has a resident webserver module that works in conjunction with server 50 to identify,optionally dynamically generate, and serve content elements 94 upondemand.

Now that general architecture of a system in ac dance with the presentinvention has been disclosed, attention turns to FIG. 2, which disclosesa method for logging into system 10 (FIG. 1). In the first processingstep shown in FIG. 2 (202), a user initiates a session on system 10 byrequesting the global login script “session_config.” It will beappreciated that the term “session_config” merely provides anillustrative name for the global login script and that the technology ofthe present invention is by no means limited to this name or the scriptdescribed.

The request for “session_config” originates on client 20 and is sent toserver 50 where it is processed by login module 60 of web server 58.Upon receiving request 202, login module 60 creates a “session_config”global login script (204). Processing step 204 is advantageous relativeto systems that have static global login scripts because it allows forthe incorporation of highly variable information. This highly variableinformation includes, for example, system settings such as up-to-dateserver redirect information, server content address changes, directedadvertisements, and messages. An exemplary “session_config” is found inExample 1 below. Each line of data has an associated numeral. Theremaining text in the example describes the purpose of select data.

EXAMPLE 1

Version tag that identifies the latest home NIM version

-   -   (1) </SESSION_CONFIG VERSION=“alpha:3”

Upgrade event that is sourced when home NIM version is outdated

-   -   (2) <UPGRADE=http://www.NIM.com/QuickOpen.exe>

LOCATION OF SERVER-SUPPORTED FUNCTIONALITY Default base address forserver supported functionality

-   -   (3) <METHODS BASEURL=http://neo.NIM.com/servlet/NIMServer/>    -   (4) <ADD_USER URL=“addUser/>    -   (5) <GET_USER URL=“getUser”/>    -   (6) <SET_USER URL=“setUser/>    -   (7) <GET_SES_CONFIG        URL=http://www.NIM.com/home_NIM/s_cnfg.xml”/>

Server-based functionality for setting password

-   -   (8) <SET_PASSWORD URL=“setPassword”/>

List of all publically available NIMs

-   -   (9) <GET_MASTER_NIM_LIST URL=“getMasterNIMList”/>    -   (10) <GET_ALL_CONFIG URL=“getAllConfig”/>    -   (11) <SET_ALL_CONFIG URL=“setAllConfig/>    -   (12) <SET_ALL_STATS URL=“setAllStats”/>    -   (13) <GET_NIM_TEMPLATE URL=“get_NIM_Template”/>

Location of server-side NIM and pack sharing functionality

-   -   (14) <ADD_SHARE URL=“addShare”/>    -   (15) <GET_SHARE URL=“getShare”/>    -   (16) <AUTH_TEST URL=“DOeCHO?AUTH=TRUE”/>

Redirect information

-   -   (17) <DO_REDIR URL=“doRedir”/>    -   (18) </METHODS>

Flexible content layer that defines default NIM frame appearance,including the default appearance of the frame of a home NIM

-   -   (19) <FRAMES>

Default NIM frame appearance

-   -   (20) <NIM>    -   (21) <IMAGES        BASEURL=http://www.NIM.com/home_NIM/NIM_FrameImages/>    -   (22) </NIM>

Default home NIM frame appearance

-   -   (23) <HOME_NIM>    -   (24) <IMAGES BASEURL=http://www.NIM.com/home_NIMImages/>    -   (25) </HOME_NIM>    -   (26) </FRAMES>

Location of system NIM templates

-   -   (27) <NIMs>    -   (28) <ADD TEMPLATE=“http://www.NIM.com/ . . .        /add_NIM_XML.xml”/>    -   (29) <HELP TEMPLATE=“http://www.NIM.com/ . . .        /help_NIM_XML.xml”    -   (30) <LOGIN TEMPLATE=″http://www.NIM.com/ . . . /login2.xml”/    -   (31) </NIMs>    -   (32) </SESSION_CONFIG>

Line 1 of the exemplary “session_config” of Example 1 provides theversion tag for the expected version of the home dot system thatcorresponds to the “session_config” script. In one embodiment, clientparser application 38 determines whether it is up-to-date using theinformation in line 1. If client parser application 38 determines thatit is outdated, an upgrade request is made in accordance with theinstructions provided by the UPGRADE flag of line 2. In one embodiment,the UPGRADE flag in line 2 of Example 1 describes the location of anexecutable program, one of skill in the art will appreciate that thisflag can in fact reference any form of instruction, including a flatfile, a web page, a script, a symbol, or an address.

Lines 3 through 18 in Example 1 define the functionality that isprovided by a server, such as server 50. For example, line 8 of Example1 provides the location of a set of instructions that are called when auser requests a password change. Furthermore, line 9 of Example 1provides the location of master list of NIMs that are publicallyavailable. Lines 14 and 15 of Example 1 provide the location ofspecialized server-side functionality that allows users to share datasuch as NIM definitions.

Lines 19 through 26 of Example 1 define where the default appearance ofa NIM and a home NIM are found within system 10. Lines 27 through 31define a collection of system NIMs. A system NIM is any type of NIM thatis to be distributed to each user of system 10. In some embodiments,system NIMs are used to provide a core functionality. In Example 1, line28 defines a NIM that provides users with a convenient mechanism forcollecting additional NIMs. Line 29 defines the location of a NIM thatis invoked when the user presses a help button associated with a homeNIM. Finally, line 30 defines the location of a NIM that is used to loginto system 10.

Returning to FIG. 2, once login module 60 has created “session_config,”it is sent back to requesting client 20 (206). When a “session_config”is received by client 20, client parser application 38 parses the globallogin script in order to identify a reference to a login constructor 62(208). Login constructor 62 is a server-based module that generates aconstruct that allows a user to log into system 10. When client parserapplication 38 locates the reference to login constructor 62 in“session_config,” a request for a login construct is directed to theidentified reference (210). In Example 1 above, the reference to thelogin construct is provided in line 30. On line 30, the global variable“LOGIN TEMPLATE” is assigned the URL address “http://www.NIM.com . . ./login2.xml.” Client parser application uses the URL assigned to theglobal variable “LOGIN TEMPLATE” to make a request for a loginconstructor 62 that is directed to this URL. When login constructor 62receives a request for a login construct, it generates a login construct(212).

Login construct 148 (FIG. 3B) illustrates a type of login construct thatis generated in one embodiment of the present invention duringprocessing step 212. Before the login construct is executed on client20, a schematic such as logo 146 (FIG. 3A) is displayed on output means42. As illustrated in FIG. 1, login constructor 62 is a component of webserver 58. However, there is no requirement that login constructor 62 bea component of web server 58. In fact, login constructor 62 is astandalone software program in some embodiments of the present inventionwhereas in other embodiments, login constructor 62 is merely a script,such as a PERL script, that is processed by an interpreter programnative to server 50. In still other embodiments, login constructor 62 ismerely a simple flat file that includes a set of instructions that areinterpretable by client parser application 38. In such embodiments,login constructor 62 is the login construct. In embodiments in which alogin construct is dynamically generated, it is possible to introducelast minute changes in the login construct. Thus, an advantage of theexemplary login process shown in FIG. 2 is that there are multiplestages in which updated information is used to customize the loginprocess based on the environmental variables.

Once a login construct has been prepared by login constructor 62, it istransferred back to client 20 (214) (FIG. 2) and executed in conjunctionwith client parser application 38 (216). The login constructs of thepresent invention are a form of NIM. Therefore, one function ofprocessing step 216 is to obtain the login NIM content 64 (FIG. 1)specified by the login construct from server 64. In login construct 148,for example, the login NIM content includes the shape and functionalityof “Exit button 160,” message 150, the shape and functionality of “Newuser” button 152, the functionality of “Forgot it?” button 154, andlogin panel 156. When processing step 216 is completed, the user usesthe login construct to provide a login identifier (218).

In FIG. 3B, a user has provided the login identifier “Galliani.” Thedefinition of login identifier as used in the present invention is to bebroadly construed. In some embodiments, login identifiers include aunique name and a corresponding password. In other embodiments, a loginidentifier does not have a password. This is particularly the case whenthe user is a guest or a new user and there is no user profileassociated with the user.

Working in conjunction with client parser application 38, the loginconstruct accepts the user login and sends it to server 50 forvalidation (218). As illustrated in the exemplary system of FIG. 1, webserver 58 includes a login validation module 66 to verify the loginidentifier provided by user (220). Typically, processing step 220involves a look-up operation in which the login identifier is used toquery user profile database 76 for an unprocessed or raw user profilethat matches the login identifier. In embodiments that include apassword, validation step 220 includes a password verification step.Successful completion of processing step requires entry of a valid loginidentifier sequence in processing step 218. When processing step 220 hasbeen successfully completed, the raw or unprocessed user profilecorresponding to the login identifier is obtained from user profiledatabase 76 (FIG. 1) (222) and is processed by user profile processmodule 68 to produce a processed or finalized user profile that isdelivered to client 26 (226). In sonic embodiments, a user profile 76includes user contact information, such as the name, address, telephonenumber and email address of a user. Additionally, some embodiments ofsystem 10 provide different types of access privileges. For example oneembodiment of the present invention includes developer accessprivileges, administration access privilege, and general user accessprivileges. In such embodiments, the access privileges that have beengranted to a user are stored in the user profile 76 associated with theuser.

The processed user profile includes a reference to each NIM in system 10that is associated with the login identifier provided in processing step216. One of the NIMs referenced by the processed user profile is thehome NIM that corresponds to the login identifier provided in processingstep 216. When executed in conjunction with client parser application 38in processing step 226, the home NIM provides a mechanism for accessingeach of the NIMs referenced by the processed user profile Like the loginconstruct, the home NIM includes several components, including pull downmenus and screen manipulation functionality. The reference to the homeNIM in the processed user profile includes the system 10 address of eachof these components. Therefore, in one embodiment, construction of thehome NIM in processing step 226 involves one or more requests to server50 and/or server 82 for content (228) that is then rendered (230) inaccordance with the home NIM description provided in the processed userprofile. In some embodiments, the home NIM is distinct from other NIMsin the sense that a large proportion of the home NIM in such embodimentsis pre-compiled. Such embodiments are advantageous because some of thefunctionality provided by the home NIM requires substantial client 30processing resources. Therefore, to minimize such processing resourcerequirements, many aspects of the home NIM are pre-compiled in someembodiments. In other embodiments, however, the home NIM has a structurethat is substantially the same as a regular NIM. In such embodiments,simple script commands are used to identify the NIM as a home NIM.

Upon completion of processing step 230, the user is granted access toall of the technologies of the present invention, including the abilityto view multiple NIMs simultaneously, collect new NIMs, customize NIMs,and share customized NIMs with other users. An exemplary processed userprofile is provided in Example 2. Once again, each line of data isidentified with a numeral, while the remaining text in the exampledescribes select data. In some embodiments, the user is granted specificprivileges and the extent to which the user is granted access to system10 is regulated by the types of privileges that have been granted to theuser.

EXAMPLE 2

-   -   (1) SAMPLE PROCESSED USER PROFILE    -   (2) <ALL CONFIG>

NIMs AND PACKS THAT CORRESPOND TO THE USER

-   -   (3) USER

NIM definition 1

-   -   (4) <NIM DOMAIN=“ZDNet” GLOBALID=“1” KND=“news”    -   (5) <FRAME BACKGROUNDCOLOR=#FFFF00” COLLAPSED=“FALSE”    -   (6) FIXHEIGHT=“TRUE” FIXWIDTH=“TRUE” NAME=“ZDNet Breaking News”    -   (7) PIXELHEIGHT=“275” PIXELWIDTH=“235” X=“RIGHT” Y=“TOP”>    -   (8) <TITLE COLOR=#000000” JUSTIFY=“RIGHT” TEXT=“ ”/>    -   (9) <TITLEBARIMAGE DOWN=http://www.NIM.com/ . . .        /feed/titlebar.gif    -   (10) HOVER=URL address to a first GIF file <param 1> . . .        <param N>    -   (11) INACTIVE=URL address to a second GIF file <param 1> . . .        <param 2>    -   (12) NORMAL=URL address to a third GIF file <param 1> . . .        <param 2>    -   (13) <BOTTOMBARIMAGE DOWN=http://www.NIM.com/ . . .        /feed/bottombar.gif    -   (15) HOVER=URL address to a fourth GIF file <param 1> . . .        <param 2>    -   (16) INACTIVE=URL address to a fifth GIF file <param 1> . . .        <param 2>    -   (17) NORMAL=URL address to a sixth GIF file <param 1> . . .        <param 2>    -   (18) </FRAME>    -   (19) <MENU/>    -   (20) <CONTROL_LAYOUT HEIGHT=“1” HEIGHTSCALES=“TRUE” WIDTH=“1”    -   (21) WIDTHSCALES=“TRUE”><CONTROL CLASS=“Browser” HEIGHT=“1”    -   (22) ID=“1” KIND=“A” LEFT=“0” TOP=“0”    -   (23) URL=http://www.mandala.com/cgl/zdnet/zdfeedl.cgi        WIDTH=“1”/>    -   (24) </CONTROL_LAYOUT>    -   (25) <CATEGORIES/>    -   (26) <EVENTS/>    -   (27) </NIM>

NIM definition 2

-   -   (28) <NIM DOMAIN=NIM DOMAIN 2 GLOBALID=‘2’    -   (29) </NIM>

(92) NIM definition N

-   -   (30) <NIM DOMAIN=NIM DOMAIN 2 GLOBALID=‘N’    -   (31) </NIM>

Pack definition 1

-   -   (32) <PRESET TITLE=“New DotPack”>    -   (33) <NIM GLOBALID=“1” X=“RIGHT” Y=“TOP”/>    -   (34) <NIM GLOBALID=“2” X=RIGHT Y=“320”/>    -   (35) </PRESET>    -   (36) </SHARE>

Last state of the home NIM

-   -   (37) <LASTSTATE>    -   (38) <PRESET TITLE=“ ”>    -   (39) <NIM GLOBALID=“1” X=“RIGHT” Y=“TOP”/>    -   (40) <NIM GLOBALID=“2” X=RIGHT Y=“280”/>    -   (41) </PRESET>    -   (42) <HOMENIM COLLAPSED=“FALSE” HEIGHT=“134” X=616” Y=“109”/>    -   (43) </LASTSTATE>    -   (44) </ALL_CONFIG>

Example 2 describes a representative processed user profile inaccordance with the present invention. In general, a processed userprofile includes three major components: (i) a definition of each NIMassociated with the user, (ii) a description of each pack associatedwith the user and, (iii) the last state of each home NIM associated witha user. In Example 2, the definition of each NIM associated with theuser is found on lines 4 through 31. Specifically, lines 4 through 31describe NIM definitions I through N. In Example 2 there is only onepack associated with the user. This pack, entitled “New DotPack,” isfound on lines 32 through 35 of Example 2. The final major component ofthe processed user profile found in Example 2 is the last state of thehome NIM, which is defined on lines 37 through 43. This code stores thelast state of the home NIM. Such last state information includes whetherthe home NIM was collapsed, and the position of the home NIM on thescreen.

When the user wishes to log out of system 10, the processed user profileis transferred from client 20 to server 50. When web server 58 receivesthe processed user profile, it passes the processed user profile to userprofile database manager 100. User profile database manager 100 storesthe processed user profile as the unprocessed user profile 76corresponding to the user. In some embodiments, such a storage operationinvolves a conversion process. For example, advertisements or specificsystem NIM definitions are stripped from the processed user profile inorder to convert the processed user profile to the unprocessed userprofile 76 that corresponds to the user. In some embodiments, theprocessed user profile is periodically transferred, in its entirety orincrementally, from client 20 to server 50 and saved in the mannerdescribed in the log out procedure above. Such timed periodic or eventbased backup procedures are possible because NIM definitions areefficiently described, thus the absolute size of a processed userprofile remains relatively small. Accordingly, timed backups of aprocessed user profile to user profile database 76 are possible withoutextensive use of system 10 bandwidth or server 50 resources.

At this stage, a system (FIG. 1) and a login procedure (FIG. 2) inaccordance with the present invention has been disclosed. Although thesystem and login procedure was discussed using an example where only onehome NIM was associated with a user, it will be appreciated that, insome embodiments, any number of distinctly different home NIMs areassociated with a user. Furthermore, a user can simultaneously executemultiple instances of a particular home NIM on client 20 or, indeed, anynumber of different home NIMs. In one embodiment, a developer ormerchant provides a user with a highly customized home NIM that providesspecialized functionality. In such embodiments, the user collects thehome NIMs and, therefore, a processed user profile includes adescription of more than one home NIM.

Attention now turns to some of the advantages and features of thepresent invention. In FIG. 4, a visual manifestation of the home NIM 162is illustrated. One advantage of the home NIM, which is an advantagethat is common to NIMs in general, is that the content of the NIM is nottrapped in a third party viewer. In fact, the home NIM definitionregulates the actual appearance of the home NIM. The home NIM definitionis formed by general parameters and commands found in “session_config”as well as customized parameters and commands in the processed userprofile. The division of the home NIM definition between a system levelfile and a user level file represents a balance in the tension betweenthe need for a system 10 host to insure a consistent level of quality,through the proper implementation of general parameters and commands,and the desire of each user to create highly customized home NIMs. Lines20 through 22 of Example 1 provide an example of general parameters thatare defined in “session_config.” Lines 23 through 25 define the sourcelocation of home NIM frame images. In home NIM 162 (FIG. 4), such homeNIM frame images include the image used to represent buttons 164 through174, and menu tabs 1 d 178. Furthermore, lines 20 through 22 of Example1 define the location of other images that are used to construct defaultNIMs. An example of user initiated home NIM customization is found inlines 33 through 39 of Example 2, which define a “LASTSTATE” definitionfor the home NIM, including the dimensions of the visual manifestationcorresponding to the home NIM on line 38 (HEIGHT=“134” X=“616” Y=“109”)and indicates that the home NM is not collapsed upon startup(COLLAPSED=“FALSE”).

The visual manifestation of home NIM 162 illustrates additional benefitsand features of a home NIM in accordance with the present invention.When a user selects tab 176, a list of the NIMs that are present in theprocessed user profile associated with the user is displayed in viewer180. As disclosed in more detail below, a user has the option toassociate a collection of NIMs into an object termed a “pack”. The packreferences some subset of the NIMs associated with a user as well asassociated state information. This arrangement includes, for example,whether a visual manifestation corresponding to each MM is displayed onoutput means 42 or not, the dimensions of each visual manifestation, andthe position of each visual manifestation. The name of each pack isstored in the processed user profile. A user reviews packs associatedwith the user by selecting tab 178 (FIG. 4). In FIG. 4, the user onlyhas one pack, “Customized DotPack” 182. When the user selects pack 182,each NIM in the pack is restored in accordance with the stateinformation stored in the pack definition.

In total, FIG. 4 represents a typical visual experience provided by oneembodiment of the present invention. In addition to home NIM 162, visualmanifestations 184 and 186, corresponding to two additional NIMs in theprocessed user profile, are displayed. Visual manifestation 184 providesfunctionality that allows a user to manage an address book, scheduleappointments, or create groups and plan activities. Visual manifestation186 represents a NIM that provides time and date information.

FIG. 5 shows the visual manifestation of home NIM 162 of FIG. 4 with tab176 selected. Accordingly, each of the NIMs in the processed userprofile associated with the user is listed in list 188. The user canactivate any of the listed NIMs by clicking on the NIM name. In additionto the NIMs in list 188, home NIM 162 includes core NIMs that aredefined in “session_config.” In the “session_config” of Example 1, coresare found on lines 28 and 29. Specifically, line 28 provides the addressof an XML-based definition for the add template functionality associatedwith button 172 in FIGS. 4 and 5, and line 29 provides the address of anXML-based definition for the help template functionality associated withbutton 174 in FIGS. 4 and 5.

Importantly, the user can categorize NIMs using filter 190. Categoriesinclude such topics as sports, personal, weather, etc. Furthermore, theuser can add NIMs to the processed user profile associated with the useras well as delete NIMs. There are a variety of mechanisms that enable auser to add a NIM to the processed user profile. One mechanism is toreceive links to NIMs from other users of system 10 (FIG. 1), asdisclosed below. Another mechanism is to toggle button 172 in order toactivate a visual manifestation associated with NIM 192 (FIG. 5).

NIM 192 provides a system that enables users to add select NIMs to theiruser profile with a single click or keystroke sequence. NIM 192 includestab 194 that allows the user to select premiere NIMs and a general tab196 that allows the user to review a general catalog of NIMs that ispresent in NIM templates database 74 (FIG. 1). In one embodiment, when auser selects a NIM in list 198 (FIG. 5), the NIM is added to list 188and is incorporated into the processed user profile associated with theuser. In this way, the user can collect NIMs of interest to the userusing a single mouse click. By illustration, consider the case in whicha user selects the NIM “AnyDay Calender” in list 198. In response tothis selection, a definition of the NIM “AnyDay Calender” is obtainedfrom NIM templates database 74 and is copied directly into the processeduser profile associated with the user. Furthermore, the title of theselected NIM, “AnyDay Calender” is added to list 188. Finally, a visualmanifestation that corresponds to the NIM “AnyDay Calender” is displayedon output means 42 (FIG. 1). As a result, the display illustrated inFIG. 5 adopts the appearance illustrated in FIG. 6.

In FIG. 6, the NIM “AnyDay Calendar” appears at the top of list 188.Furthermore, a control 101 associated with the NIM “AnyDay Calendar” inlist 188 is filled, indicating that the NIM is currently active.Additionally, as illustrated in FIG. 6, a visual manifestation 103corresponding to NIM “AnyDay Calendar” appears on the output means. Theuser has the ability to toggle this NIM between an inactive and activestate by selecting control 101. (105) In one embodiment, the user isprovided with the option of (i) incorporating a NIM selected in list 198into the processed user profile or (ii) transiently executing the NIM onclient 20. Furthermore, when the user receives NIMs from other users,the user has the option to transiently operate the received NIMs onclient 20. If the user decides to keep the transient NIMs at a laterdate, the user has the option to add the transient NIMs to the processeduser profile at that time. Thus, in such embodiments, the usereffectively has the option to “preview” NIMs before adding them to theprocessed user profile. This is advantageous because it reduces thechances of filling the user profile with undesirable NIMs. Such afeature is particularly advantageous in the case of novice orinexperienced users of system 10. Furthermore, one of skill in the artwill appreciate that the concept of transient NIM execution raises thepossibility of executing NIMs on a client 20 during a period of time inwhich the user is not logged into system 10. For example, consider a NIMthat is executed on a client 20 after a user initiated response to a webpage advertisement presented in web browser 36. Although the user is notlogged into web server 58 and therefore does not have a processed userprofile resident on client 20, the user can execute the NIM on client 20on a transient basis. Furthermore, if the user wishes to add thetransiently executed NIM to the user profile 76 associated with theuser, the user can log into web server 58 and then add the NIM to theprocessed user profile that is delivered to client 20 as a function ofthe log in process.

Another important feature of the present invention is the ability forusers to share NIMs with each other. For example, if a user wishes toshare the NIM “AnyDay Calendar” that was added to list 188 in FIG. 6,the user clicks “share” button 170 (FIG. 6). In response, panel 105 isdisplayed (FIG. 7). Because “share” button 170 is pressed while tab 176is active in the illustration provided by FIGS. 6 and 7, panel 105 listseach of the NIMs associated with the user. If, however, “share” button170 is pressed while tab 178 is active rather than tab 176, panel 105will list each of the packs associated with the user instead of each ofthe NIMs. Returning to the situation illustrated in FIG. 7, the usershares a NIM with other users by selecting the NIM to be shared fromlist 107 and then toggling button 109 “Share via email.” In oneembodiment, the user has the option to select multiple NIMs from list107 using predefined keystroke operations. For example, in oneembodiment, the user selects multiple NIMs by clicking on several of theNIMs in list 107 with a mouse button while depressing the “shift” buttonon the keyboard. When a user decides not to share a NIM and panel 105 isdisplayed, the user presses cancel button 111 and panel 105 isdismissed.

When a user toggles “share via email” button 109 at a time when one ormore NIMs in list 107 have been selected, the definition of eachselected NIM is copied from the processed user profile associated withthe user into a container and the container is sent to server 50 (FIG.1). In the embodiment shown in FIG. 1, the container is received by webserver 58. Web server 58 includes instructions for routing the containerto sharelink database 78 where the container is stored. When thecontainer is stored, a unique identifier is assigned to the container.Although a large number of different mechanisms for generating a uniqueidentifier are practiced in accordance with this aspect of theinvention, in one embodiment, the unique identifier assigned to thecontainer upon storage in sharelink database 78 can be subsequentlyprocessed to form a URL address that specifically references thecontainer within the context of system 10. In one embodiment, after aunique identifier has been assigned to the container, an e-mail programis launched on client 20 and the user is requested to designate therecipients of the designated NIMs. Then, each recipient is provided withthe unique identifier associated with the container in an e-mailmessage. When the recipient clicks on the unique identifier, a call ismade for a copy of the associated container from sharelink database 78and the container is delivered to the client 20 associated with therecipient.

As is readily apparent upon review of FIG. 7, the user has the option tosize and position the visual manifestation that corresponds to each NIM.Furthermore, by toggling controls, such as toggle button 101 (FIG. 7),the visual manifestation of a NIM is toggled between an on state and anoff state. Such functionality is highly advantageous. First, by usingthis functionality, the user has the option to create uniquearrangements. Second, NIM developers have the ability to control thedefault position and size of NIMs as well, and can therefore produce anarrangement of NIMs to further specialized purposes. Finally, becausethe NIMs of the present invention are not trapped in third partyapplications that have a set of undesirable features such banner ads,the utility and overall appearance of an arrangement of NIMs is enhancedand adopts an independent value. Using the technology disclosed in thepresent invention, the user collects an assortment of NIMs and arrangesthem in a customized fashion. The user has the option to “capture”favored arrangements into constructs known as packs, which have beenbriefly discussed previously.

FIGS. 8 and 9A illustrate the formation of a pack using the arrangementof NIMs illustrated in FIG. 4. The process begins when the user togglesbutton 164 “Make Pack” in FIG. 4. In the embodiment illustrated by FIGS.8 and 9A, panel 113 (FIG. 8) is displayed when the user toggles button164 (FIG. 4). Panel 113 advises the user to open and arrange each of theNIMs that are to be included in a pack. In the case of FIG. 4, forexample, such an arrangement could include the arrangement of NIMs 184and 186. The user indicates that specified NIMs are in a desiredarrangement by selecting button 115 “Next” (FIG. 8). When button 115 istoggled, prompt 113 is terminated and prompt 117 is displayed to promptthe user for a name to associate with the designated pack. The userindicates that a name 119 has been provided for the pack by selecting“Done” button 121.

In the embodiment shown in FIG. 8, the user further has the option toreturn to panel 113 and rearrange the specified NIMs before committingto pack creation by selecting the “Back” button 123. In the situationillustrated in FIG. 8, the user has provided the name “New DotPack.”FIG. 9A illustrates the state of the visual manifestation correspondingto home NIM 162 after the user has selected “Done” button 121 (FIG. 8).Specifically, the name “New DotPack” is added to pack list 125 and tab178 is activated to display the user pack list rather than the user NIMlist that is displayed when tab 176 is activated. Furthermore, inresponse to the user selection of “Done” button 121 in FIG. 8, areference to each NIM specified by the user is collected into a pack,along with some state information, and the pack is stored in theprocessed user profile associated with the user. Representative stateinformation for each NIM stored in a pack includes whether the NIM wascollapsed and the position of the NIM. In some embodiments, the stateinformation includes the dimensions of the last visual manifestationcorresponding to the NIM to have been displayed on output means 42.

FIG. 9 illustrates pack 139, which is delineated with a dashed box. Pack139 includes five NIMs 133. Each NIM 133 includes two primarycomponents, a viewer 135 for viewing content and a frame 137 forproviding user functionality. Each viewer 135 provides a platform forreviewing machine readable information, such as HTML, dHTML, images,imbedded ActiveX and Java applications, JavaScript, CSS, StreamingMedia, and/or Flash. Furthermore, in some embodiments, viewer 135provides functionality for processing digitally recorded sound. Observethen that each NIM of the invention utilizes machine readableinformation that is easily retrieved from a specified address. If thecontent provider of this information desires to change the machinereadable information, changes can be made and then delivered the nexttime that the machine readable information is addressed. This stands incontrast to prior art techniques in which updates to executable code canbe relatively difficult to distribute.

Each frame 137 provides functions and controls for manipulating thevisual manifestation of the NIM 133 corresponding to the frame. Forexample, some frames 137 include a dismiss button 141. When the userclicks on dismiss button 141, the corresponding NIM 133 is dismissed.Additionally, some frames 137 include a menu button 143. When the userclicks on button 143, a menu appears. In one embodiment, the menu is apull down menu and the menu items are defined in the corresponding NIMdefinition. In an abstract example, the NIM definition provides a menudefinition of the format:

Menu 143-(I)-“Get more NIMs” URL

where (I) refers to the N.sup.th element of the menu that is activatedwhen menu button 143 is pressed, “Get more NIMs” is the menu elementname, and URL is the event or web address that is called when the userselects the N.sup.th element of the menu associated with button 143.

The developer has full control over all aspects of the appearance andfunctionality of NIM frame 137. Thus, a NIM developer has the ability tocontrol, for example, the functionality located at any corner of frame137, functionality placed along the top or bottom of the frame, or onthe sides of the frame. As an illustration, frame 137-3 includes acontrol button 145 that allows the user to resize the visualmanifestation of NIM 133-3. One of skill in the art will appreciate thatthe bottom row of NIM frame 137 could have any number of buttons,including a forward control, a backward control, and similar controls,each of which provides the user with distinct functionality.

An advantage of the present invention is that it is possible to embedcommands that affect frames 137 in the content of the computer readablemedia delivered to frame viewer 135. The use of embedded commandsprovides NIM developers with powerful tools and additional flexibility.For example, a developer can use embedded commands, such as the menucommand above, to design a NIM that has a context sensitive help menu.Each time a particular event occurs, the developer changes the contentof the help menu using embedded commands. For example, when a sound fileis delivered to a NIM, the sound file may be attached to a set ofembedded commands that provide sound manipulation functionality in theform of a pull down menu. Elements of such a pull down menu include acommand for saving the sound file to disk, commands for fast forward,stop, and play, and commands for sound enhancement. After the sound filehas been played, embedded commands are used in this example by thedeveloper to reset the menu associated with button 143 to some defaultstate. One of skill in the art will appreciate the benefits andadvantages of a frame 137 that is capable of being modified based oncommands embedded in the machine readable media delivered to thecorresponding viewer 135. The developer can use presentation tools, suchas adding transient help buttons, resizing the visual manifestation ofthe NIM, changing the frame border color, changing the title of theframe, and changing the frame border patterns, to create a moreeffective application.

One of the advantages of the disclosed pack system is that it provides aconvenient mechanism for rapidly assembling NIMs that track diversesources of information. Furthermore, when a useful set of NIMs iscollected into a pack, the user can share the pack with other usersusing the same procedure previously identified for sharing one or moreNIMs. It will be appreciated that in some embodiments, NIMs arecommercial applications and that appropriate use of packs provides anadditional dimension for application development. Therefore, in someembodiments, pack recipients are subscribers to a service provided by apack developer. In other embodiments, pack recipients are purchasers orlicensees of packs. In still other embodiments, pack recipients receivepacks developed by friends, family members, or business associates.

The technology of the present invention further provides a set of NIMmanagement tools to help a user manage displayed NIMs. In someembodiments of the present invention, these management tools areprovided by visual management module 114 (FIG. 1). Two such NIMmanagement tools are, in fact, properties that are associated with NIMs,namely magnetism and snapping. The property of magnetism is exhibitedwhen a visual manifestation corresponding to a first NIM is dragged ormoved near a visual manifestation corresponding to a second NIM. Whenthis occurs, the two NIMs exhibit a magnetism that causes the first NIMto accelerate toward the second NIM. However, when the visualmanifestations are within a predetermined distance of each other, theNIMs snap together. In one embodiment, the predetermined distance thattriggers the two visual manifestations to snap together is a gap ofabout five pixels. While the above discussion describes the principlesof snapping and magnetism based on a pair of NIMs, there is in fact nolimitation on the number of NIMs that can be snapped together andfurthermore, the principle of magnetism is not dependent on whether aNIM is in fact snapped to another NIM or not.

An additional management tool, illustrated in FIG. 9A, provides amechanism for selecting multiple NIMs and for moving the NIMs in acoordinated fashion. In FIG. 9A, visual manifestations 162, 184 and 186corresponding to respective NIMs are locked together. In response, halo127 is drawn around the selected locked visual manifestations tographically notify the user which NIMs are locked together. As mentionedpreviously, the user has the option to position NIMs as a coordinatedgroup. For example, in one embodiment, when halo 127 is displayed andthe user moves mouse arrow 129 after selecting one of the visualmanifestations corresponding to a locked NIM, a target manifestation 131is displayed to indicate to the user the position that the selected NIMswill be relocated to if the user clicks a mouse key. In someembodiments, target manifestation is a shadow image of the NIMs withinhalo 127 rather than the box depicted in FIG. 9.

The present technology further provides additional methods forcontrolling visual manifestations of NIMs. For example, in oneembodiment, the user has the option to select multiple NIMs by pressinga predefined key such as the keyboard “Ctrl” key, before selecting aspecified NIM. While continuing to depress the control key, the user hasthe option to select additional NIMs and add the corresponding NIMs to agroup. The user then has the option to move each of the NIMs in a singlecoordinated fashion as a group. Furthermore, by entering a designatedkeyboard or mouse sequence, the user has the option to move a single NIMeven in situations where the NIM is in a group. In one embodiment inaccordance with this aspect of the invention, the user clicks the visualmanifestation corresponding to a locked NIM that the user wishes to movein an independent manner and the user does not click the visualmanifestation when the user wishes to move the NIM in a manner that iscoordinated with the other NIMs. Additional features of the presentinvention include the option to select rows or columns of NIMs usingspecialized control sequences. For example, in one embodiment of thepresent invention, the user selects a column of NIMs by clicking on aNIM while holding down the alphanumeric character “c” on the keyboard.

It will be appreciated that one advantage of the present invention isthat it is possible to display multiple NIMs and that each NIM providesa specialized visual experience. Therefore, NIM alignment tools areadvantageous because they allow users to quickly make room on outputmeans 42 for additional NIMs and/or to produce highly styled NIMarrangements. Accordingly, the present technology provides a specializedfeature to rapidly align NIMs. This technology is illustrated in FIG.10. The technology works in conjunction with the tools for selectingmultiple NIMs. In FIG. 10A, the user selects the visual manifestations147, 149 and 151 corresponding to respective NIMs using, for example,the column select feature disclosed above. Then, the user pushes theselected NIMs against boundary 153. In one embodiment, boundary 153 isthe horizontal or vertical edge of output means 42. In anotherembodiment, all visual manifestations corresponding to NIMs aredisplayed in a single viewport such as a window. In such embodiments,the horizontal and vertical edges of the window each represent aboundary. FIG. 10B illustrates how visual manifestations 147, 149, and151 are automatically aligned when they are pushed against a boundary,such as boundary 153. In some embodiments, the relative alignmentbetween the visual manifestations is preserved even after themanifestations are moved in subsequent action by the user. The presenttechnology further allows for the rearrangement of NIMs along aparticular axis. For example, if NIMs are substantially oriented along avertical axis as shown in FIG. 10B and the user wishes to realign theNIMs on the horizontal axis, all the user has to do is push thecollection of NIMs against a horizontal border. For example, when theuser pushes visual manifestations 147, 149 and 151 against border 155,the visual manifestations realign to conform to border 155 thusresulting in the view depicted in FIG. 10C.

The features of the home NIM of the invention have been fully described.Attention presently turns to the architecture and operation ofindividual NIMs utilized in accordance with the invention.

In one embodiment of the invention, after a user has logged into thesystem, as discussed above in connection with FIGS. 1 to 10, the userinterface 40 displays the home NIM 162 as shown in FIG. 5. The home NIMtypically includes a list of NIMs 188, referred to in FIG. 5 as“MyDots.” These are NIMs which have been “collected” by the user. Thelist of collected NIMs, along with their associated definitions, isstored on the server in the user profile database 76, and downloadedfrom the application server 50 in response to a request from the clientparser application 38. The local copy of the processed user profile isthen further processed when the user collects or uses NIMs.

Collected NIMs may be opened or closed by clicking on the control buttonnext to the NIMs name or on the NIM's name itself, in list 188, and allNIMs may be closed by clicking on the “all off button’ 166. The user mayplace NIMs into categories in a list of categories 190, which can beedited by clicking on the-Edit” button 168. New NIMs may be added to theuser's collection of NIMs by clicking on the “Get” button 172.

FIG. 5 also shows a NIM 192 with a list of NIMs 198, which may bepreviewed and/or collected by the client 20. The user may preview orcollect a NIM by clicking on the associated name of the NIM, e.g.,“eHOW”. The steps taken to provide the NIM to a user are shown in FIG.11. After logging in (step 240) the user clicks on the name of a NIM,and the client parser application 38 sends a request including theNIM_ID of the NIM definition, to the applications server 50 via thetransmission channel 44 (step 241). Alternatively, the user may click ona NIM link before logging in, for example if the link has been e-mailedto the user, and then, after clicking on the link, log in. In anotheraspect, the user could view, but not collect, a transient NIM withoutever logging in.

After the user is logged in and has clicked on the NIM, the applicationsserver 50 retrieves the NIM definition from the NIM template database 74using the NIM ID, in step 242, and provides it to the client 20 in step243. The client 20 receives the NIM definition from the applicationsserver 50 in step 244, and the client parser application 38 creates aframe in the display of the user interface 42 in step 245. In step 246,the client 20 requests the necessary content elements 94 stored at theURLs identified in the NIM definition from the corresponding contentserver 82. The content server 82 transmits the content 94 in step 247,and in step 248 the client parser application 38 places the content inthe viewer, which is enclosed by the frame, allowing the user to previewthe NIM. Alternatively, the client parser application 38 may simplycollect the NIM, adding it to the user's processed user profile.

The user may then view the NIM on the user interface display 42, and mayinteract with the NIM much in the same way as a user may interact withInternet content or web applications. This may change the NIM from itspresent, “raw” state to a used state reflecting alteration or use of theNIM by the user. For example, the user may direct the NIM to differentcontent within the NIM if the NIM content enables the user to do so. Or,the user may provide information to the content server 82 which allowsthe NIM to be personalized. The user may additionally be given theoption of changing the size of the frame.

If the user collects the NIM, the NIM will be added to the user's listof collected NIMs such as the list 188 shown in FIG. 5. Additionally,the client parser application will add the NIMs definition to theprocessed user profile, and, on logout, send the processed user profileto the application server 50. Thus, the NIM's “state” will be preserved.Alternatively, the client parser application may collect the NIMautomatically, without waiting for a user command, by adding the NIMdefinition directly to the processed user profile.

If the NIM's state has been altered by the user or by the content—if forexample, the user has directed the NIM to Internet content other thanthe initially-displayed content, provided personalizing information, orchanged the properties of the frame, or if the content itself has causedan alteration in the NIM—this alteration will be reflected in the NIMdefinition stored in the user profile database 76. Information whichpersonalizes the resulting content, instead of being stored in a“cookie” on the client's hard drive, can be stored as part of the NIMdefinition. This advantageously permits personalization of content, suchas web content that is associated with the NIM content and the user,without storing a cookie on the client 20.

A user may also access a NIM which has been previously collected, andpossibly altered by use as explained above. As previously described, theuser profile 76 includes NIM definitions for NIMs which have been viewedand collected by each user. A screen shot showing NIMs 188, which havebeen previously collected by a user is shown in FIG. 5. The steps takento provide the user with NIMs which have been previously collected areshown in FIG. 12.

As discussed above, on login (step 250) the user's profile is retrievedby the client parser application 38 in the client 20 (step 251 and 252).The user's profile, stored in the user profile database 76, includes theNIM definition for each of the NIMs previously collected, and possiblyaltered, by each user. The NIM definitions, as discussed above, includesthe NIM frame definition and the definition of the controls for fillingthe viewer within the frame with content. After log in, a local copy ofthe processed user profile is stored on the client 20, and this copy isfurther processed as the user collects new NIMs, or uses new orcollected NIMs such that the NIMs are altered.

When the user clicks on the name of a collected NIM (step 253) theclient parser application 38 creates a frame in the display 42 of theuser interface 40 in step 254. At step 255, the client 20 requests thenecessary content elements 94 stored at the URLs identified in the NIMdefinition from the corresponding content servers 82, which provide thecontent 94 in step 256. It will be appreciated that these URLs need notbe the same as the initialization URLs in the “raw” NIM definitionstored in the NIM template database 74 on applications server 50, and infact the content servers need not be the same content serverscorresponding to the initialization URLs. In step 257, the NIM parserapplication 38 places the content in the NIM frame, and the NIM is thenfully opened.

FIG. 13 illustrates a data structure for a NIM definition. As discussedabove, a NIM is defined as a frame that contains a collection ofcontrols, or functional units, such as a web rendering control or a GIFrendering control. The NIM frame surrounds a viewer, which displays theaddressed content. The MM has a defined layout or arrangement of thecontrols, and defined initialization input data, e.g. data and URLS, foreach control or element, in the NIM. NIM definitions are available tothe client parser application via NIM links. The NIM links “point” toNIM definitions, which include all the information needed to build a NIMframe and fill the NIM with NIM content. Thus, NIMs links are easilycollected, associated into packs, and shared by users.

In one embodiment, the NIM definitions are defined using ExtensibleMarkup Language (XML), so that the NIM as a whole—the frame and thecontent within the viewer—is advantageously as flexible as standard webcontent. NIMs are extremely flexible, because the definition of the NIMis content, rather than compiled code. The NIM definition defines thestructure of the NIM, and everything that is visible in a NIM is basedon standard Internet content, such as HTML, dHTML, or GIFs, and isreferenced or pointed to by the NIM definition. An “application”-typeNIM, such as a web calendar or web mail, may be changed by the user, bythe content provider, or by other content, while advantageously avoidingthe need to distribute and support a hard-coded compiled application.The definition of a NIM thus includes everything that is needed for theNIM to be rendered and filled with Internet content.

As shown in the exemplary embodiment of FIG. 13, the definition of a NIMincludes tags that identify the NIM 270, define and configure the NIMframe 271, specify and layout the controls 273 in the NIM viewer, andspecify parameters to initialize all the NIM's components with contentor data.

In one embodiment, a NIM is identified by three ID strings 270:GlobalID, Domain and Kind. A GlobaliD is used when the MM definition iswithin a share. It is unique with respect to other NIM tags in theshare. A NIM's domain is a unique label for the owning company ordeveloper of the NIM, such as “dodots.com.” Finally, a NIM's kind, whichis specified by the NIM's developer, is a helpful identifier for findingthe NIM, but need not be unique. Examples of possible NIM kinds include“mp3”, “scriblets,” and “calculator.” As discussed above, a NIMdefinition will typically be written in a format which facilitatessharing of data over the Internet, such as XML. An XML specification forthe NIM identification strings, for one embodiment of the inventionfollows. The bold text identifies NIM definition data, while theremaining text describes the data.

GLOBALID=“string” Used only within <SHARE> tags. This GLOBALID must beunique with respect to other <NIM> tags in this <SHARE>.

DOMAIN=“string”

Unique label for the owning company of this NIM. In theory, NIMs may belimited to communicating with NIMs only from their own domain.

KIND=“string”

Helpful identifier for finding such a NIM from another NIM. Does nothave to be unique.

The NIM definition also includes the definition of a frame 271, whichspecifies the frame size and shape, and optionally the frame orientationand/or location on the user's screen. The space within the frame is thecontrol space or viewer; visible controls are distributed within thecontrol space or viewer.

The NIM definition may optionally include controls for: a titlebar; aNIM menu with flexible menu entries; an exit button; and a bottombar. Atypical layout for these components is: titlebar at the top of thecontrol space, with menu on the left and exit button on the right, andthe bottombar at the bottom.

The titlebar component gives the user a place to grab and drag the NIMin a windowed environment. In one embodiment, it is implemented as a GIFrendering control that can be targeted to a local or remote titlebarimage. The titlebar will preferably have a fixed height and width thatis a function of the NIM's width. The titlebar is preferably capable ofbeing located at any position on the periphery of the NIM. Overlay textcan also be specified to layer on top of the titlebar image. Thebottombar may be implemented in a similar fashion, but typically willnot include text overlay. The titlebar and bottombar may be filled inwith initialization data from a fixed data file, or alternatively withInternet content from, example, an initialization URL.

In one embodiment, a menu definition 271 is also included in the NIMdefinition. The menu includes items and actions of the NIM provider'schoosing. For example, menu items may include the title “browse”associated with the action of targeting a full-screen browser or anotherNIM, and retrieving content for that browser or NIM from a specifiedaddress such as a URL. Logging off, or directing the NIM to anotheraddress or URL, are also possible menu action items. Menu action itemsthat require communication of messages between the NIM and another NIMmay also be provided—for example, opening another NIM, or changing thecontent of another NIM that is already open. Communication of messagesbetween different parts of the system is discussed below.

An XML specification for a frame, titlebar, bottombar and menu, for oneembodiment of the invention follows:

<FRAME>

<TITLE>

-   -   TEXT=“string”    -   JUSTIFY=−“LEFT”|“CENTER”|“RIGHT”    -   COLOR=“#XXXXXX”    -   PIXELWIDTH=“integer”        Width in pixel units. Overrides WIDTH attribute.        PIXELHEIGHT=“integer”        Height in pixel units. Overrides HEIGHT attribute.        WIDTH=“integer”        Width in NIM units. Default value is 1.        HEIGHT=“integer”        Height in NIM units. Default value is 1.        X=“integer”|“LEFT”|“CENTER”|“RIGHT”        Initial X position in screen coordinates. Default is center.        Y=“integer”|“TOP”|“CENTER”|“BOTTOM”        Initial Y position in screen coordinates. Default is center.        FIXWIDTH=“TRUE”|“FALSE”        Default is false.        FIXHEIGHT=“TRUE”1“FALSE”        Default is false.        BACKGROUND COLOR=“#XXXXXX”        Default is white.        <TITLEBARIMAGE>        JUSTIFY=“LEFT”|“CENTER”|“RIGHT”        TILELEFT=“integer”        TILERIGHT=“integer”        NORMAL=“URL”        DOWN=“URL”        HOVER=“URL”        INACTIVE=“URL”        <BOTTOMBARIMAGE>        JUSTIFY=“LEFT”|“CENTER”|“RIGHT”        TILELEFT=“integer”        TILERIGHT=“integer”        NORMAL=“URL”        DOWN=“URL”        HOVER=“URL”        INACTIVE=“URL”        <MENU>        Contains zero or more <ITEM> tags.        <ITEM>        TITLE=“string”        TOOLTIP=“string”        ICON=“URL”        ID=“string”        Must be unique.        <ACTION>RECIPIENT=“address” MESSAGE=“string”

As shown in FIG. 13, the NIM definition also includes layout anddefinition of the controls 273. A control may be visible and render somesort of visual or text display, either static or dynamic. A control maybe hidden, for example a functional element that is not necessarilyvisual such as a Java control. The control definition 273 includesidentification of the types of controls, the layout of the controls, andinitialization information. In one embodiment, NIM controls arespecified and identified by class, kind and ID. Class defines the typeof NIM control and is not unique. Kind is a useful identifier selectedby the developer, and again is not unique. The NIM ID is unique within auser's processed profile.

Different classes of controls may be used. For example, a control may bea web rendering object, which can render web content such as HTML,dHTML, images, imbedded ActiveX and Java applications, JavaScript, CSS,Streaming Media, and/or Flash. Alternatively, a control may be anyobject capable of rendering any kind of computer readable media, such asa GIF rendering object or an custom-designed object to display aparticular kind of information. Alternatively, a control may be anobject capable of processing any kind of application logic, such as aJava module. For example, an on-line brokerage firm could implement acustom stock-chart-rendering control, and define a NIM to use thiscontrol.

As discussed above, the control space is located within the frame, andone or more controls can be flexibly positioned within the controlspace, and these controls may include a titlebar and a bottombar, aswell as other controls. The location of controls is specified by thelayout in the definition of the controls 273 within the NIM definition.In one embodiment, the controls are laid out or positioned within theNIM frame according to a flexible grid. In this embodiment, the NIMdefinition allows the control space to be subdivided into equal verticaland horizontal units, and then for the controls to be positioned andsized within the control space.

A control definition will typically include initialization data. Forexample, where a control is a web rendering object, the definition willinclude initial URLs. When the NIM is opened, the control will navigateto the initial URLs to obtain content and render the NIM. If the controlis a GIF, the control could retrieve the GIF file from a content serveror from the application server. A NIM definition may optionally includeadditional tags identifying initialization parameters for differentplatforms: for example, a URL is suitable for a PC, but a “P-URL” may beprovided as well, pointing to content suitable for users viewing NIMsthrough a personal digital assistant (PDA) or similar device.

Controls are typically installed on the applications server, and may beupdated after installation by the applications server. The home NIMcode, downloaded when the client becomes “NIM-enabled,” includes thethen-existing controls. Controls are updated as new controls areinstalled on the server or when a user requests a NIM that requires anew control. The server may then may download such updates to the clientparser application, for example on log-in. The NIM framework allows anycontrol to be positioned and initialized in a control space in a NIM, asdiscussed above.

An XML specification for control definition and layout, in accordancewith one embodiment of the invention, follows:

<CONTROL_LAYOUT> Contains zero or more <CONTROL> tags.

WIDTH=“integer” Divides control space into this many evenly spacedcolumns. Default is 1.

HEIGHT=“integer” Divides control space into this many evenly spacedrows. Default is 1.

WIDTHSCALES=“TRUE”|“FALSE” Default is true.

HEIGHTSCALES=“TRUE”|“FALSE” Divides control space into this many evenlyspaced columns. Default is 1.

<CONTROL>

CLASS=“string” Class may be “Browser,” “GIF reader,” or other object forrendering computer readable media.

KIND=“string”

ID=“string” Must be unique with other controls in this NIM.

LEFT=“integer” X position of the control in container unites. Default is0.

TOP=“integer” Y position of the control in container units. Default is0.

WIDTH=“integer” Width in container units. Default is 1.

HEIGHT=“integer” Height in container units. Default is 1.

URL=“URL” This is read if and only if this control is of class“Browser”. This is the URL to which this control navigates. Otherwise,may include address for other control content, e.g. GIF address inapplications server.

<CATEGORIES> Contains zero or more <CATEGORY> tags.

<CATEGORY> Adds the NIM to this category. This is the only waycategories are specified; i.e. there is no master category list.

NAME=“string” This is the name of the category.

A NIM definition may also optionally include home NIM categories 274. Ahome NIM category used by home NIM 204 is a convenient way for a user tokeep track of collected NIMS. When a user adds a NIM to a category 204,the category is added, as a string element, to the categories element274 of the NIM definition in the user profile. For example, a user maycategorize a particular NIM as “entertainment,” or “news,” or“reference.” This category will then be added to the categories element274 of the MM definition.

A NIM definition may also optionally include an events element 275,which defines actions to certain NIM events. For example, the OnCloseevent, when a NIM is closed, may be assigned a specific and targetedaction, similar to a menu item. An XML specification for the eventelement in a NIM definition, in accordance with one embodiment of theinvention, follows:

<EVENTS>

<ONCLOSE>

Executes this action list on close.

<ACTION_LIST>

Contains zero or more <ACTION> tags.

<ACTION>

RECIPIENT=“address”

MESSAGE=“string”

A sample NIM definition, in an XML file format in accordance with theabove specification, follows:

<NIM DOMAIN=“calculator” KIND=“basic”>

<FRAME CLASS=“Standard” BACKGROUNDCOLOR=“#FFFF00”

WIDTH=“6” HEIGHT=“4” FIXWIDTH=“TRUE” FIXHEIGHT=“TRUE”>

<TITLE TEXT=“Basic Calculator” COLOR=“#0000FF” JUSTIFY=“LEFT”/>

<TITLEBARIMAGE JUSTIFY=“LEFT” TILELEFT=“1” TILERIGHT=“1”

NORMAL=“ ”INACTIVE=“ ”HOVER=“ ”DOWN=“ ”/>

<BOTTOMBARIMAGE JUSTIFY=“LEFT” TILELEFT=“1”

TILERIGHT=“1” NORMAL=“ ”INACTIVE=“ ”HOVER=“ ”DOWN=“ ”/>

</FRAME>

<MENU/>

<CONTROL LAYOUT WIDTH=“1” HEIGHT=“1”>

<CONTROL CLASS=“Browser” KIND=“A” ID=“1” TOP=“0” LEFT=“O”WIDTH=“1”HEIGHT=“1”

URL=“http://www.dodots.com/dots/Calc/CALCULATOR2.htm”/>

</CONTROL LAYOUT>

</NIM>

The first line of this definition establishes the identification of theNIM definition, as discussed above: it is in the domain “calculator,”and the kind of display is “basic.”

In one embodiment, the domain will be the domain name associated withthe content provider. The domain name is a unique label for the provideror developer of the NIM. The NIM's “kind” is a helpful identifier forlocating the NIM, and need not be unique. A NIM may also be identifiedusing a GlobalID, when the NIM is being shared. Since the NIM defined bythis XML file is not being shared, it does not have a GlobalID.

The second line of the example XML NIM definition establishes the sizeand appearance of the NIM frame, defining a NIM viewer in which the NIMcontent will be placed. The third line ensures that the height and widthof the frame are fixed—that is, the size of this frame cannot beadjusted by the user. The fourth and fifth lines establish the title ofthe NIM—“Basic calculator”—and its location. The next four linesestablish the location and placing of the titlebar and bottombar, andrelevant images, e.g. mouse-over. Thus, the first part of the exampleNIM definition defines the NIM frame. The definition of a frame,titlebar, menu and other aspects distinguish a NIM from a browser—thecontent provider has control over the frame size and every aspect of theNIM's appearance, whereas when a browser is used, the content providerhas to adapt to the browser display size, and browser titlebar, menu,logo and other aspects cannot be controlled by the content provider.

The rest of the NIM definition identifies, positions, and initializesthe NIM's controls, which, in this case, are contained by the NIM frame.In this example, the next few lines establish that a single control willstart in the upper left corner of the NIM viewer, that the control is ofthe type “browser,” or web-rendering, and that the initialization URLfor the control is www.dodots.com/dots/Calc/CALCULATOR2.htm. This URL istypically referred to as the “initialization URL,” because it is wherethe NIM looks for NIM content when it is opened. Where the control is oftype “browser,” the content will typically be HTML content. However, anystandard Internet content—HTML, dHTML, flash, streaming media, or Java,for example—may be used. As discussed earlier, a control, could includetypes other than a browser. The final two lines of the XML file closethe definition file.

It will be appreciated that the NIM is designed such that contentconsumes the entire frame. In one embodiment, the content for thecorners of the frame—the menu and the exit button—and the frame sizingimages are served by an application server and referenced when the userlogs in. Everything else is developed and served by a separate NIMdeveloper. This differs fundamentally from the current approach toproviding web content, in which there is a strong distinction betweenthe viewer application—the browser—and the web page or web content.Using present browser-type technology, the content is trapped within theviewer. To obtain a cohesive application feel and access to applicationfeatures, the current alternative is to develop custom clientapplications. NIMs allow a developer to provide an application feelwithout developing custom client applications.

NIMs and the client parser application have a messaging architecture—theNIM messaging architecture, or NMA—that enables NIMs, controls, and theclient parser application to communicate. Messaging, in combination withthe NIM definition, gives the content of a NIM access to theapplication/rendering program—the client parser application—and to otherNIMs, allowing true application behavior. The NIM definition, discussedabove, is accessible, flexible, and may be changed by a NIM or a userwhile the NIM is in use, even after it's been rendered.

The content provider, the user, or other NIMs can change a NIM. Forexample, the content—which includes the titlebar and menu elements—maybe changed by the NIM provider by simply enhanced NIM content, using 20messaging, so that NIMs can exhibit true application behavior. Forexample, an online brokerage firm can go beyond providing a NIM thatrenders stock tracking charts, and allow users to trade on-line via asecond NIM that can interact with other NIMs such as the first NIM tohelp facilitate the activity.

A NIM can be changed by its content, or by another NIM, using messaging.This enables a NIM to, for example, notify a user of events, such as achange in content. A NIM could, for example, remain open, but in acollapsed mode, until a particular event occurs, and could then eitherexpand to normal size, or open another related NIM. For example, if aparticular stock hits a predetermined price, the stock tracking chartNIM discussed earlier can notify the user by expanding, by popping up amessage, or by opening another NIM (such as a stock trading NIM).Alternatively, the NIM could notify the user of a particular event bycoming into focus or changing size or content. These changes could alsobe made by sending messages from a content or applications server to theNIM.

As illustrated in FIG. 14, all elements of the system can send andreceive NMA messages. Message routing between NIMs, from a NIM to itself(that is, between e.g. the frame elements and a control, or one controland another), and from NIMs to the system, are handled by a messageinterface module 106, which is part of the client parser application 38in the client 20. In one embodiment, the message interface module 106resolves addressing queries, executes system-level commands from theNIMs such as “close all NIMs,” and passes messages between NIMs. Themessage interface 106 may also communicate messages to controls such asthe browser class controls, for example “navigate the addressed NIM'sbrowser control to the argument URL.” Alternatively, the messageinterface module 106 may route a message to an application or contentserver (not shown in FIG. 14) for expanded functionality. In oneembodiment, the message interface module 106 uses an HTTP request toaccess an application program interface (API) call, with data optionallybeing sent and received in XML format. For example, the messageinterface 106 could send a message providing user input, such as creditcard information to a credit processing module on a web server 82.

In one embodiment, an NMA message has two components: a recipient, oraddress, and the message body. Both are represented as strings. Theaddress may specify an exact NIM, a kind of NIM or control, a domain, orthe system, meaning the overall home NIM display. For example, in oneembodiment, the address may be in the form:

#<NTM specifier>:<control specifier>

if the communication is between NIMs in the same domain, or

#<domain>:<NIM specifier>:<control specifier>

or

#<domain>:<NIM specifier>:<NIM id>:<control kind>:<control id>

if the communication is between NIMs in different domains, or

#system

if the communication is to the system.

In one embodiment, if the address is not properly specified it defaultsto #system. The message interface 106 in the client 20 can flexiblyallow, restrict MM addressing or sending messages—for example, themessage interface can ensure that only certain NIMs can send message toa particular NIM. This allows NIM developers to develop coordinated NIMsthat can interact, by sending messages to e.g. change content or openone another, without allowing other NIMs to interact with theircoordinated NIMs.

In one embodiment, a specifier in n address may be the uniqueidentification of the NIM, control or domain in question:<specifier>:=<ID>. Alternatively, where the kind of NIM or controlreceiving the message is important but the specific NIM or control isnot, the specifier may address a message to the closest matchingrecipient using a search criteria: <specifier>:=<kind>#<searchcriteria>. The kind should be a type of NIM or control that is installedin the system. Search criteria may be, for example, “any,” “open,” or“closed.” Finally, where the control is being specified, the specifiermay be a symbol, such as “.”, indicating that the message is addressedto the sending NIM. For example, in one embodiment, the address #systemsends the message to the system. The address #. sends the message to theNIM which sent the message. The address #7 sends the a message to theNIM with the identifier 7. The address #B#open:5 sends a message to thecontrol with the identifier 5, in the first open dot of kind B found inthe system.

In one embodiment, certain NIMs will have privileges to send particularmessages to certain NIMs, and not to other NIMs. For example, NIMs in adomain may be permitted to send control messages to other NIMs in thesame domain, but not to NIMs in other domains. Thus, a NIM provider mayhave control over messaging between NIMs in his domain, and prevent NIMsin other domains from changing NIMs in his domain. Alternatively, NIMproviders may coordinate with NIM providers in other domains, permittingcertain messaging privileges between some of the NIMs in theirrespective domains. The HomeNIM and other system NIMs, such as the loginNIM, which are in the system domain, may have certain messagingprivileges that no other NIMs have, such as logging the user out orclosing all the currently-open NIMs.

In one embodiment of the invention, the second part of the message, thebody, is represented as a string of characters. Messages may be sent tothe client parser application, to the frame of a NIM, or to a control.Messages may be specific, defined messages, as shown in the followingexamples, or may be any javascript, which may be sent in or out of NIMcontent. Examples of defined messages to the client parser application,in one embodiment, are:

Application Message<arg> Function Refresh Refreshes the user's profile.#have-NIM <NIM-address> Check if the user has the specified NIM as partof the user's profile. #delete-NIM <NIM-address> Remove the specifiedNIM from the user's profile. #get-screen-width Returns the width of thescreen. #get-screen-height Returns the height of the screen.#close-all-NIMs Closes all open NIMs. #get-NIM-ids <NIM-address> Returnsthe NIM ID of the specified NIM.

Messages can also be sent from a NIM to itself, or to another NIM, andthe identified actions or functions, specified in the body, areperformed on the receiving NIM. The following are examples of messagesto a NIM for one embodiment of the invention:

Defined NIM Message<arg> Function #set-size<width><height> Sets the sizeof the NIM. #set-width<width> Sets the width of the NIM.#set-height<height> Sets the height of the NIM.#set-position<x-pos><y-pos> Sets the position, of screen, of the NIM.#set-title<title> Sets the title of the NIM. #collapse Collapses, butdoes not close, the NIM. #uncollapse Uncollapses the NIM.#set-user-sizable<width true/ false> Establishes whether the NIM is<height true/false> sizeable by the user #set-background-color<color>Sets background color of the NIM.#set-title-text-justify<justify-keyword>

The above examples of NIM messages may, in one embodiment of theinvention, be sent to a NIM by another NIM. For example, a user mayprovide input to a NIM, for example a stock tracking chart NIM,indicating an interest in another NIM, such as a stock trading NIM. Thecurrent NIM may then send an “open” message to the second NIM to openit, if it wasn't already open. The current NEM may then send a navigatemessage (see below) that may include an argument, such as a URL or othercontent pointer, so that the second NIM could be opened to a specificURL indicated by the first NIM.

Finally, messages may be sent to a control of a NIM, either by the NIMitself, another control, the HomeNim system, or another NIM. Asexamples, the following control messages are provided in one embodimentof the invention:

Defined Control Message Function ##<any javascript> Run any javascriptin the control, e.g. javascriptin a browser-type control. #show Setvisibility control within a NIM. #hide Set invisibility of a controlwithin a NIM. #get-size Get size of control. #get-address Query forunique ID of a control by kind. #navigate Navigate the control.

Control messages may be used by a NIM, addressed to its own control, orto the control of another NIM. Control messages may also be sent by theHomeNIM, or by the applications server or content server.

An example of a message to a NIM iswindow.external.PostMessage(“#.:”,“#collapse)” this is a message from aNIM, to itself, collapsing the NIM. Another example of a message from aNIM to another NIM is“window.external.PostMessage(“#mp3#any:”,“#open”)”, which is addressedto a NIM with the kind “mp3,” but only if it is in the same domain asthe sending NIM. The body of the message instructs the message of typemp3 to open. An example of a javascript message is“window.external.PostMessage(Vmp3#any:1”, “33play( ))”, which sends amessage to the mp3 NIM control that calls the javascript function play().

The operation of the home NIM and individual NIMs has been described.Attention presently turns to different techniques used in accordancewith the invention 25 to host NIMs.

As shown and described in relation to FIG. 1, the application server 50includes a NIM Management Modulel 12, a NIM Templates Database 74, aShareLink Database 78, and a user profile database 76.

FIG. 15 is a diagrammatic illustration of an embodiment of the NIMManagement Modulel 12. NIM Management Modulel 12 may contain the NIMTemplates Database 74 and the ShareLink Database 78, discussed infurther detail below. NIM Management Module 112 may also contain content402 for filling in a NIM frame or for rendering Internet pages.Alternatively, content 402 may be stored elsewhere, such as on a Webserver similar to the server 82 shown in FIG. 1. As discussed above, thecontent preferably contains Internet content such as HTML (HypertextMarkup Language), dHTML, and images.

In addition, Management Modulel 12 preferably contains executableprocedures 403 for controlling and managing the NIM system. Theseprocedures 403 may include: a Collection procedure 404 for obtaining newNIMs; a Sharing procedure 405 for sharing NIMs with others; Developmentprocedures 406, such as a DevZone procedure 407 and a DevNIM procedure408, for creating, modifying or deleting NIMs; Publishing procedures409, such as a PubZone procedure 410 and a PubNIM procedure 411, forpublishing NIMs so that they are publically accessible; andAdministration procedures 412, such as an AdminZone procedure 413 and anAdminNIM procedure 414, for administering the system. It should be notedthat the NIM sharing procedure, discussed in further detail below, maybe processed by either the Server module (102 of FIG. 1), or the Sharingprocedure (405 of FIG. 15). Control and management of the server and theNIM Management Modulel 12 components will now be discussed in furtherdetail.

FIG. 16 is a diagrammatic illustration of an embodiment of the NIMTemplates database 74. In this embodiment, NIM Templates database 74primarily stores XML NIM definitions in their initial unmodified stateas initially designed by a partner and which have not been altered by auser in any way. The unmodified NIMs are also referred to as “Raw NIMs”.The NIM Templatesdatabase 74 is used as the starting point for thedevelopment of NIMs which may later be customized or modified by a user,developer, or system administrator, as discussed below.

For ease of explanation, the individual or organization that controlsthe server (50 of FIG. 1) will hereinafter be referred to as the systemprovider and the individual or organization who supplies the contentwill hereinafter be referred to as a partner. It should be understoodthat a provider, partner, user, developer, and administrator of thesystem may be distinct entities, the same entity, or a combination ofboth. Furthermore, as discussed above, each of the above entities isassigned access rights or privileges which permit or forbid that entityfrom performing different actions on the system.

FIG. 16 illustrates an embodiment of a NIM Template database 74. A NIMidentification number (NIM_ID) 416 is stored in a NIM Template table41.5 in the NIM Templates database 74. A Raw NW, identified by itsincludes a plethora of RAW NIM characteristics, including, but notlimited to, a Raw NIM creation date 417, which indicates when the NIMwas created and is useful when searching for NIMs created during aspecific time, a Raw N.I.M definition module 418, and the NIMIndexcategories 422 in which the NIM has been categorized. Each NIM whencreated in typically classified into one or more NIM Index categories bythe developer, such as “Applications”, “Business”, “Entertainment” and“News”.

Each NIM is fully configurable and definable. The NIM definition module418 contains details defining the NIM, such as the look-and-feel 419, ofthe Raw NIM, initialization URLs (Uniform Resource Locators) 420, and alocation 421 of where the developer would like the NIM to open on ausers's computer screen. The look and feel of the NIM is the appearanceand function of the NIM interface. The look and feel may characterizethe frame or skeleton layout, the graphics used to represent certainfunctions, such as opening and closing the NIM, whether the frame issizable, and the appearance and operation of menus in the frame.

The definition module 418 may also contain Initialization URLs 420 whichreference resources containing content. The content resources may beHTML (Hypertext Markup Language), dHTML, images, programs such as Javaapplets, or any other file supported by HTTP. The Initialization URLs420 contains the name of the protocol required to access the resource, adomain name that identifies a specific computer on a network, such asthe Internet, and a hierarchical description of a file location on thatspecific computer. These files or resources are then used by the homeNIM to fill in the frame and controls with content. In addition, thedefinition module 418 may contain other details such as the location 421on a user's computer screen where the NIM should initially open.

The NIMIndex may be used to search for, learn about, and collect NIMs.The

NIMIndex is typically accessed from either a Web browser, such asInternet Explorer® or Netscape Navigator® or from the home NIM, 108 ofFIG. 1. A user may search for NIMs by, or according to, any field of theNIM Templates table 415 via the NIMIndex.

A user accessing the NIMIndex from a Web Brow typically navigates to amain NIMIndex web page such as that shown in FIG. 17. FIG. 17 is anillustration of the main NIMIndex Web page 423. A user typicallynavigates to main NIMIndex Web page 423 from a NIM home-page (notshown), or while anywhere within the NIM Web site by clicking on the“Collect the DOtS™” link 424 in a menu 425. A user may search theNIMIndex by entering a search term in a form 426 and clicking on the“Search” button 428 which implements the Collection Procedure (404 ofFIG. 15) to search the NIM Templates database (74 of FIG. 15) for NIMsthat match the query. In one embodiment, the NLMIndex may be searched byNIM title, NIM description, or partner, as shown in the pull down menu430. The user may also browse the NIMIndex by clicking on a link 432 toa NIMIndex category 434 which will navigate the user to a NIMIndexcategory Web page 440, as shown in FIG. 18.

FIG. 18 is an illustration of a single NIMIndex category, the“Applications” category 435, shown in FIG. 17. A list of sub-categories(not shown), as well as a list of NIMs 442 and their short descriptionsare shown in FIG. 18. A user may click on the “more detail” link 444 tobe taken to a page displaying a full description (discussed later inrelation to FIG. 29B) of the NIM, shown in FIG. 19.

Navigation of the Internet generally occurs through the use of URLs(Uniform Resource Locators), which are the addresses of files orresources accessible on the Internet. The type of resource depends onthe Internet application protocol. Using the World Wide Web's protocol,the Hypertext Transfer Protocol (HTTP), the resource can be an HTML(Hypertext Markup Language) page, an image file, a program such as aJava applet, or any other file supported by HTTP. The URL contains thename of the protocol required to access the resource, a domain name thatidentifies a specific computer on the Internet, and a hierarchicaldescription of a file location on the computer and usually takes theform:“URL=protocol://machine.name[:port]/directory/document.name′?[&argu-ments] ” The “protocol” is the Internet protocol used to reach thedocument or resource. On the Web, the “protocol” is typically HTTP, butit can take any number of forms, such as ftp (file transfer protocol),file (a local file), gopher (gopher protocol), mailto (electronic mailaddress), news (Usenet news), telnet and tn3270 (interactive sessions),wais (wide area information servers), or the like.

The “machine.name” is the name of the host come where the documentresides (such as www.NIM.com). The “:port” portion of the address isoptional and is only necessary when a resource is accessible through anon-standard TCP port number. Although the standard port number for HTTPis 80, there are numerous Web servers on the Internet that usenon-standard ports, such as port 8000.

The NIM system, however, may also utilize a proprietary NIM protocol. Anexample of a URL using the proprietary NIM protocol is:“NIMS:?NIMTemplate=<N/M_ID>”

The NIM protocol URL is used to collect, distribute, and share NIMs.When collecting NIMs the NIM protocol URL is referred to as a NIMLink.When distributing or sharing NIMs the NIM protocol URL is referred to asa ShareLink.

The “NIMs:” term defines the NIM protocol or scheme and is alwaysfollowed by a colon. The “?NIMTemplate=<NIM_ID” is an argument, where adollar sign (5) and a question mark (?) are used to denote path and/orsearch elements. It should be noted that no path is supplied (i.e.:“//path/to/something”). The argument instructs the client parserapplication (38 of FIG. 1) how to handle a user's selection of a NIMprotocol URL and what the NIM protocol URL must do. For example, toobtain a NIM, the argument might read “NIMTemplate=123′, to obtain aShare (discussed below) the argument might read “Share=123”, to obtain aPack (discussed below) the argument might read “Pack=123”, etc. Theargument can be used to cause the client parser application to doanything within it's system of functionality by specifying new argumentsets to build new types of special client parser application links.

In one embodiment, the address for where the client parser application(38 of FIG. 1) searches the system (10 of FIG. 1) for the NIM Templateor ShareLink database (74 and 78 of FIG. 1) is specified within theprocessed login script or session_config, although it couldalternatively be specified within the NIM protocol URL. When a userclicks on a NIM protocol URL (from any where you can place and click ona link, for example in a browser, in a NIM, in email, in a document,etc.), the client parser application processes the NIM protocol URL inthe same manner as a browser processes HTTP links and an email programprocesses mailto links.

When a protocol URL takes the form of a NIMLink, the client parserapplication responds by obtaining the NIM definition from the NIMTemplate database, optionally adds the NIM to the user's processed userprofile (unless the NIM has been specified to be opened in transientmode, which may be specified in the argument), and optionally opens theNIM on the user's display screen.

In one embodiment, by default, unless specified otherwise, a NIM will beadded to a users collection (transient—false) and will be opened(open—true). A NIMLink with arguments may look as follows:“NIMS:?NIMTemplate&transient=true” or “NIMS:?NIMTemplate&open=false”.More than one additional argument could be added by appending anotherargument to the URL which may read as “&argument=value”.

A ShareLink (discussed below) is similar to a NIMLink and may read“NIMS:?share=123”, where 123 is the SHARE ID referencing the sharemodule within the ShareLink Database. Pack Links (discussed below)typically read as “NIMS:?pack-123”, where 123 is the PACK_ID referencinga pack module within the NIM Template Database.

FIG. 19 is an illustration of a full description of NIM content 446. Agraphic of the opened NIM may also be displayed 448.

Once the user decides that he would like to add a NIM to his home NIM,the user clicks on the “get it now” or “Get This Dots™ NIMLink 450(FIGS. 18 and 19) which either runs the Collection procedure (404 ofFIG. 15) which obtains that NIM's NIM definition module (418 of FIG. 16)from the NIM Template table (415 of FIG. 16), or opens another Web pageas shown in FIG. 20.

FIG. 20 is an illustration of a Web page 452 which might be displayed tothe user once the user has clicked on the NIMLink 450. The user ispresented with an option of either collecting the NIM 456, or if theuser does not have the home NIM application, the user may first downloadthe home NIM by clicking on “Get the homeDotIm” 454. Once the userclicks on the download the NIM button 456, the Collection procedure (404of FIG. 15) obtains that NIM's NIM definition module (418 of FIG. 16)from the NIM Template table (415 of FIG. 16).

The Collection procedure (404 of FIG. 15) transmits the NIM definitionto the user's home NIM, which optionally opens the MM and saves the NIMdefinition module (418 of FIG. 16) on the user's local processed userprofile. All NIM definition modules (418 of FIG. 16) on the user'scomputer may subsequently be saved to the user profile database, asdiscussed earlier in this writing. Alternatively, a “preview” button maybe provided which transiently displays the NIM on the user's computerscreen without adding the NIM to the user's local processed userprofile. The user may also search the NIMIndex from their home NIM.

FIG. 21 is an illustration of the main home NIM graphical user interface(GUI) 464, similar to that shown in FIG. 5. The home NIM displays a listof all NIMs 466 that the user has collected. Furthermore, any NIMs thatthe user has collected in groups or packs, can be accessed by clickingon the “My Dotpacks'” tab 468. One way to obtain new NIMs is to click onthe “Get” button 470, which opens the NIM shown in FIG. 22.

FIG. 22 is an illustration of a get new NIM GUI 474. A list of all NIMs476 (or a featured subset) that may be collected by the user aredisplayed. Clicking on the “More Dots” tab 478 (shown in FIG. 23)displays further NIMs which may be collected.

When a user selects or clicks on any of the NIMLinks 480, NIMLink 480references the NIM_ID (416 of FIG. 16) for that NIM in the NIM Templatesdatabase (74 of FIG. 16). The collection procedure (404 of FIG. 15)receives the (416 of FIG. 16) from the user, locates the NIM definitionmodule (418 of FIG. 16) corresponding to that NIM_ID in the NIMtemplates database, and transmits the NIM definition module to theuser's computer. That NIM may automatically be opened on the user'scomputer screen. The NIM is saved to the user's list of NIMs on theirhome NIM (466 of FIG. 21), and the NIM definition module is saved in theuser's local processed user profile. Alternatively a “preview” buttonmay be provided which transiently displays the NIM on the user'scomputer screen without adding the NIM to the user's local processeduser profile, as discussed above in relation to the NIMLink. All the NIMdefinitions that the user has listed on their home NIM are saved to theuser profile database either periodically, at a set time, by event, orwhen the user closes their home NIM. The technique of the inventionfacilitates a viral distribution architecture. In other words, thetechnique of the invention facilitates rampant distribution of generatedNIMs, as described below.

Users (or developers) may share NIMs they have collected, and perhapseven modified, with other users (or developers) in accordance with thisviral distribution architecture. Because the NIM definition containsbasic reference information, such as data to instantiate the NIM andURLs and other references to where the NIM content is located, a NIM iseasily and quickly distributed, collected, and shared. By-packagingInternet content and applications as NIMs and referencing the NIMs byNIMLinks, the system advantageously gives Internet content viralcharacteristics as the NIMs can easily be distributed or shared betweenusers.

Each NIM definition contains just enough information to define andinitialize the NIM's components (NIM frame, controls, etc.). Forexample, this information may contain data to configure the skeleton orframe that is filled in by NIM content from a developer's server. TheNIM definition is therefore fairly small in size (−2K), and is thereforeeasily distributable as an XML file or Blob (binary large object), whichis communicated using the same mechanisms (HTTP/HTTPS requests) asregular Web pages.

This is especially useful where a user has collected a NIM or a group ofNIMs (Packs) that he would like to send to another user. For example, auser may have an online trading NIM, calculator NIM, and stock researchMM all set up in various positions on his screen, and would like toshare the entire Pack with a friend who is remotely connected to theInternet.

To share NIMs with others, the system utilizes the Sharelink database 78of 25 FIG. 15 and the Sharing procedure 405 of FIG. 15. FIG. 24 is adiagrammatic illustration of the Sharelink database 78. NIM Sharelinkdatabase 78 stores a list of all NIMs shared by users, developers, oradministrators, in a share table 484. Each NIM or group of NIMs sharedis assigned a Share ID 486 which points to a Share module 488. EachShare Module 488 may also include a creation date 490, multiple 30individual MM definition modules 492, or multiple packs of NIMs thathave been shared (Sharepack module 494) containing multiple NIMdefinition modules 496 and 498.

FIG. 25 is an illustration of a Share NIM's GUI 500. All dots collectedby the user (466 of FIG. 21) can be shared with other users by clickingon the “Share” button 502 shown in FIG. 21. Once the user has clicked onthe “Share” button 502, the GUI 500 shown in FIG. 25 is launched. Theuser may then highlight any of the NIMs or packs of NIMs 504 he hascollected or created and thereafter share the NIMs or packs of NIMs 504by clicking on the “Share via email” button 506. It should be noted thatother means of distributing the NIMs may be used together with, orinstead of, email.

When users share NIMs or NIM packs, their home NIM application generatesa 10 share module, which may for example be an XML Blob containing theN1M definition or Sharepack modules shared. The shared NIM XML is thensent to, and saved in, the Sharelink database (78 of FIGS. 1 and 24).The Sharing procedure 405 of FIG. 15 then automatically generates ashared link (ShareLink) that references or points to the address of theshared XML on the Sharelink database. This ShareLink is then sent or 15distributed (via email or posted on a Web site) to other users.

If a user receives shared NIM(s) or pack(s) and has a home NIM installedon his client computer, then clicking on the Sharelink adds the NIM(s)to the user's home NIM and opens the shared NIM(s) on the user's screen.If a recipient of a shared NIM does not have the home NIM installed onhis computer, then the home NIM is downloaded and installed (with theuser's cooperation), the shared MM is added to his local processed userprofile, and the NIM is opened.

The NIM management module (112 of FIG. 15) may also be responsible forcontrolling and managing the development of new NIMs via the DevZone andthe DevNIM discussed below.

Because NIM content is based on existing Internet content standards(HTML, DHTML, GIFs, etc.) developers can create MM content using theirexisting Internet content development tools and methodologies.Therefore, no special hardware or software is required to develop orserve NIM content.

Furthermore, as the application server (50 of FIG. 1) hosts and deliversNIM definitions from the NIM Templates database (74 of FIG. 1)developers merely define and package the NIM content without directlyauthoring, hosting, or serving the XML NIM definitions. Therefore, nospecial hardware or software is required on the developer-side to hostand serve the NIM content, other than required for their regularInternet content.

Two means are provided for creating NIMs. First, a Developer Zone Website (DevZone) and second, a set of developing NIMs (DevNIMs). Bothmeans enable NIM developers to create, define, and modify NIMdefinitions, and to support the NIM development process which results inXML NIM definitions being added to the NIM Templates database andNIMLinks generated.

The DevZone is a Web site where NIM developers can view a list of NIMsthey have defined and/or published, add new NIMs, and categorize, view,modify, or delete their existing NIMs. The DevZone is preferablyrendered in a Web browser, is hosted on the Web server (82 of FIG. 1),and is implemented with a DevZone procedure (406 of FIG. 15). To accessthe DevZone, the developer may typically pass through a secure portal,such as by supplying a login identity and password.

FIG. 26 is an illustration of the main DevZone Web page 510. All NIMscreated by the NIM developer appear in a customized NIM list 514 thatmay only be accessed by that NIM developer. All NIMs created by adeveloper appear on the NIM list 514, unless they have been deleted bythe developer or by a system administrator. The NIM list may contain theNIM name 518, the date the NIM was created 520, and an indication 516 ofwhether the NIM is in development or accessible by the public in theNIMIndex (i.e. “in-development” or “published”).

To access the NIM definition (for modification or review) the developerclicks on a “modify” or “preview” link 524 as transient (e.g. to add theNIM to their home NIM for previewing and testing). By clicking on the“modify” link, the developer is taken to the NIM modification web page,as shown in FIG. 27. Alternatively, by clicking on the “Create a Dot”button 522, the developer is taken to a web page similar to the NIMmodification web page shown in FIG. 27, where the developer may create anew NIM.

FIG. 27 is a partial view of a NIM modification web page 530. To modifyan existing NIM, or create a new NIM definition, a developer preferablyutilizes Web forms, such as 534 to 542, or any area that containsobjects that capture user input, such as text entry spaces, check boxes,and selection buttons. Developers typically fill in forms withinformation which defines the NIM, where the details might include theNIM's name 534, the URL for any image associated with NIM 540 (as shownin FIG. 18), the URL for a detailed image 542 (448 of FIG. 19), and suchdetails as NIM frame (e.g., size of NIM, sizeable), layout of thecontrols (e.g., WebConduit control), and to specify the initial MMcontent (e.g., the initial target URLs for the WebConduit control,TitleBar, BottomBar), and any categories in which the developer wouldlike the NIM to be listed in the NIMIndex. Once the developer hascompleted or modified the forms, he may either save or delete the NIM532. If the developer selects either the development check box 536 orthe public check box 538, and then saves the NIM, the DevZone procedure(407 of FIG. 15) generates a XML NIM definition, stores the XML NIMdefinition in the NIM Templates database (74 of FIGS. 1 and 15) andreturns a NIMLink pointing to that NIM which is listed on the NIM list(514 of FIG. 26) on the developer's home NIM. The only difference beingthat once the developer selects the public check box 538 and saves theNIM, the NIM definition is published utilizing the PubZone publishingprocedure (410 of FIG. 15) to a publically accessible portion of the NIMTemplate Table (415 of FIG. 16), from where users can access, download,and collect the NIM. If the developer selects the development check box536, the NIM can only be viewed and or modified by the developer andsystem administrator. It should be noted that the DevZone only allowscontrol of certain characteristics of each NIM. Other characteristicsmay be set to default while still other characteristics can only bealtered by an administrator. In an alternative embodiment, the DevZonemay be rendered in a NIM or group of NIMs just as it was rendered in aWeb browser. In either embodiment, NIM developers fill out one or moreforms specifying NIM definition parameters, an XML NIM definition getscreated and stored in the NIM Templates. Database, and a NIMLink getsgenerated that points to the new NIM. The Developer can then view ordebug this NIM by clicking on the NIMLink to add it to his home NIM, orpreview as transient, and thereafter render it on his screen. NIMdefinitions may also be developed using NIMs and NMA messages. A 30developer may create Raw NIMs from empty NIM Templates using adevelopment NIM (the DevNIM) on the developer's home NIM.

FIGS. 28A to 28D are GUIs of a development NIM (the Dev NIM). Adeveloper may obtain a DevNIM by either collecting the DevNIM in theusual manner, as discussed above, or the system, via the systemadministrator, may share the NIM with the developer, also as discussedabove. The DevNim contains a DevNIM procedure (408 of FIG. 15) which istransmitted to the developer's home NIM, as discussed above.

To create a new NIM, the developer launches the DevNIM and enters a NIMname 550 into the DevNIM. The server then obtains an empty NIM (a NIMwith default or no initialization data and with only basiccharacteristics) from the NIM Template Database using the procedure forcollecting NIMs described above, and saves the empty NIM under thesupplied new NIM name 550 locally in the developer's processed userprofile. The developer may then modify the empty NIM to the requiredform using the DevNIM. In the preferred embodiment a pull down menu 552is provided where the developer can select which feature to modify, suchas the frame characteristics (FIG. 28B), the titlebar (FIG. 28C), orinitialization URLs for different frame or control elements (FIG. 28D).

Each time the developer modifies a setting, the DevNIM, using the DevNIMprocedure, sends NMA messages to the newly saved NIM to modify itsdefinition parameters. For example, modifying the NIMs name, size,TitleBars, BottomBars, or WebConduits (as shown in FIGS. 28A to 28C).

Unlike the DevZone, a new XML NIM definition and NIMLink is notgenerated every time a modification is made. All modifications (duringthe development cycle) are made locally to the NIM definition and arestored in the developer's processed user profile. The DevNIM embodiment,therefore, requires a separate publishing step that promotes the newlycreated NIM definition from the developer's user profile, to the NIMtemplates database on the application server.

To publish the NIM, the NIM developer categorizes the NIM and the NIMdefinition is copied from the developer's processed user profile to theNIM Templates database.

A publishing NIM (PubNIM), implemented with Publishing procedures 409,is provided to handle these functions. The PubNIM may therefore beshared or transmitted to the developer along with the DevNIM. The PubNIMcontains a PubNIM procedure (411 of FIG. 15) which controls thepublication of the NIMs to the NIM template database, as discussedabove. The PubNIM procedure sends a NIM definition module to theapplication server which receives the NIM definition module, extractsthe NIM definition from the share module, stores it in the NIM Templatesdatabase, and associates the NIM with the developer so that the NIMLinkshows up on the developer's NIM list (in their DevZone account).

Alternatively, the new NIM may be published directly from the DevNIM.Once a user is satisfied with the NIM, he may select an option whichpublishes that NIM definition to the NIM Templates database. It shouldbe noted that a developer may modify his NIMs at any time from theDevNIM.

As mentioned earlier, when a developer is first authorized to createand/or modify NIMs, or at any time thereafter, information about thatdeveloper is saved in that developer's user profile (76 of FIG. 1) onthe application server.

A developer may also create application programs using NIMs, which auser may access from his client computer. Just as client-sideapplication characteristics (sizing, position, menus) are accessible tocontent via NMA, the system may offer server-side applicationfunctionality, or toolkits, which are accessible through the NMA.

A developer can build a NIM application without implementing, hosting,or supporting complex server or client applications. By using the servertoolkits, a developer can develop N1Ms that exhibit server-applicationbehavior by focusing on implementing NIM content (just like standardInternet content).

For example, a NIM's content (an HTML page) may send a message to thesystem (or server) to request a credit card to be processed. Othertoolkit examples may include credit card billing, user profiling,targeted advertising, email, chat rooms, Internet telephonyapplications, or calendars.

Any server-side application can be made accessible through the NMA, as atoolkit, just as client-side application behaviors are made accessible.In the current implementation, server-side application functions couldbe offered by a NIM (exposed via javascript functions on a page in ahidden frame). Other NIMs could access this functionality by sending NMAmessages to this “Toolkit NIM” calling the functions. A NIM developermay therefore focus on Internet content development while accessing thefeatures, behaviors, and functionality of an application just as if hehad developed custom client and server side applications. The NIMmanagement module (112 of FIG. 15) may also be responsible forcontrolling and managing the administration of the system via theAdminZone and the AdminNIM discussed below.

A system administrator has the power to create, modify or delete users,developers, NIMs, other administrators, or NIMIndex categories,depending on that administrators access privileges. In a similar mannerto the DevZone and DevNIM, system administrators may utilize either aWeb browser administration zone (AdminZone), or an administration NIM(AdminNIM) which both make use of Administration procedures (412 of FIG.15).

To access the AdminZone, an administrator typically passes through asecure portal, such as by supplying a login identity and password. Oncewithin the AdminZone, the administrator may search for a NIM by NIM nameor title 552, category, developer, developer contact name, or status, asshown in FIG. 29A. The administrator may also selectively search forNIM's in development or publically accessible NIMs 554.

Utilizing an AdminZone procedure (413 of FIG. 15), once the required NIM20 is located the administrator may modify or delete the NIM in asimilar manner to a developer as shown in FIG. 29B, and described above.

Also utilizing the AdminZone procedure, the administrator may manageNIMIndex categories by creating new categories, modifying or deletingexisting categories, and/or adjusting the layout of the NIMs withinthose categories as shown in FIGS. 30A and 30B. For example, anadministrator may change a category's name 558, designate the categoryactive or inactive 556, or create sub-categories 560. The systemadministrator may also select a category or categories for the NIM toappear in, where each NIM may be registered in more than one category.

Finally, utilizing the AdminZone procedure (413 of FIG. 15), anadministrator may search for users, providers, or developers and adjusttheir details, as shown in FIGS. 31A and 31 B. The system administratormay, for example, change a users contact details. In addition to adding,modifying or deleting NIMs, system administrator may have the task ofreviewing NIM submissions from developers and promoting NIMs to thepublic. A submissions list of newly submitted NIMs may be displayed toan administrator, who may promote the NIM to the public or view the NIM.Once promoted, changes are made to the NIM Templates database and theNIM is automatically removed from the submissions list (again byutilizing the AdminZone procedure (413 of FIG. 15)).

The foregoing discussion has explored the inherent nature of NIMs.Attention now turns to different techniques that may be used to exploitinformation that is associated with the use of NIMs. In particular, thefollowing discussion is directed toward the accumulation of statisticalinformation that is only available in view of the architecture of thepresent invention.

Currently, the predominant method of tracking and collecting user onlinebehavior is severely limited for a number of reasons. First, mostInternet use or visitor statistics are single-dimensional (linear,sequential) because Internet content is presented to users onefull-screen page at a time. Second, users visit and leave sites sorapidly their visits are barely meaningful. Third, user's browsinghabits are often discontinuous (browsers give users navigational bypasscontrols—back, forward, home, refresh, stop, etc.). Fourth, userbehavior tracking is limited from a single site's server point of view.Current use statistics are plagued with the challenge of trackingcontinuous user behavior (especially from a cross-company perspective),with more than a single dimension of use context. Finally, because acomputer may have multiple users, or a single user may use multiplecomputers, tracking continuous user on-line behavior is extremelydifficult.

One of the advantages of the NIM system as illustrated in FIG. 1, isthat the Server 50 is able to track continuous, long-term NIM useinformation about each user. This is because the NIM server, throughcommunication with the home NIM, can track each NIM event performed byeach user. Therefore, it is possible to track each individual user'sentire NIM use activity from the moment the user downloads the home NIM.

Referring to FIG. 32, in one embodiment of the invention the followingevents may be tracked by the Event Log Module 98 (within the clientcomputer 20 of FIG. 1): home NIM Download Event 704 NIM Download Event706 NIM Display Event 708 Web Click-Through Event 710 Page-View Event712 First NIM Installation Event 714 First home NIM Startup Event 716Transient Mode Event 718 Share NIM Received Event 720 NIM Pack ReceivedEvent 722.

A home NIM Download Event 704 is logged when the user clicks on a linkto request the home NIM user application. Preferably, the start time752, and the end time 754 are recorded for this event. Also recorded isthe provider ID 750 which is a parameter (generally, an integer) thatrepresents the content provider partner who provided the link to theuser.

NIM Download Event 706 is logged when the home NIM acquires a NIM via aNIMLink. The start time 752, the end time 754, and the provider ID 750are recorded for this event. Also recorded is the NIM ID 756 which is aparameter (generally, an integer) that represents the NIM that was justdownloaded.

NIM Display Event 708 is logged when a user activates a NIM. The NIM ID756, the start time 752, and the end time 754 are recorded for thisevent. Web Click-Through Event 710 is logged whenever a user links froma NIM to a full-screen browser. This can occur when a user clicks on alink in the NIM, or it can occur automatically through the NIMmessaging, or directly through the content provider. The NEM ID 756, thestart time 752, and the Internet address 758 of the link are recorded.Page-View Event 712 is logged whenever a user views a page of contentwithin a NIM. The NIM ID 756, and the start time 752 are recorded forthis event.

First NIM Installation Event 714 is logged the first, a NIM or NIM Packis installed from a web site. This event is logged only once for eachuser account. The NIM ID 756, start time 752, and end time 754 arerecorded for this event.

First home NIM Startup Event 716 is logged when the home NIM runs forthe first time. This event is logged only once for each user account.The start time 752 is recorded for this event.

Transient Mode Event 718 is logged when the home NIM runs in transientmode. Transient mode occurs when the home NIM runs before the user haslogged in. The start time 752, and the end time 754 are recorded forthis event.

Shared NIM Received Event 720 is logged for each NIM a user receives aspart of a share. If a NIM Pack is shared, this event will be recordedfor each NIM in the shared pack. The NIM ID 756, the start time 752, andthe end time 754 are recorded for this event.

Shared NIM Pack Received Event 722 is logged for each NIM Pack a userreceives as part of a share. Thus, when a NIM Pack is shared, an Event720 will be logged for each NIM in the NIM Pack, while an Event 722 willbe logged once for the NIM Pack itself. The start time 752, and the endtime 754 are recorded for this event.

The events listed above are tracked in one particular embodiment. Otherembodiments may track more or perhaps fewer events. This comprehensiveevent tracking is possible because each user event can be identified bythe NIM Server through communication with the home NIM. Additionalevents may include tracking when a user sends a share or tracking when auser sends a NIM or a NIM Pack.

FIG. 33 shows a typical series of user actions 800 as they are trackedby the Event Log Module 98. First, a user may request to download thehome NIM application (step 802) from either a partner's web site or theNIM Server 50. The Event Log Module 98 records a home NIM DownloadEvent, as shown with field 704 of FIG. 32. The start time 752, and theend time 754 are preferably recorded. Also, the provider ID 750 of thesite from where the home NIM download request was received is recorded.

Returning to FIG. 33, the user subsequently activates the home NIM forthe first time (step 804). The Event Log Module 98 records a First homeNIM Startup Event 716, as shown in FIG. 32. The start time 752 ispreferably recorded. In addition, the home NIM is activated and the userlot yet logged in, a Transient Mode Event 718 is logged and the starttime 752 is recorded.

As shown in step 806 of FIG. 33, the user logs into the home NIM. Whenthis occurs, the end time 754 may be recorded for the Transient ModeEvent 718.

A user download of a new NIM (step 808) may be from a partner's web siteor the NIM Server. When this occurs, the raw NIM definition is copiedinto the user's User Profile 76. The event log 98 records two events.First, because this is the first NIM the user has installed, a First NIMInstallation Event 714 is recorded. The start time 752, the end time754, and the provider ID 750 of the download site are preferablyrecorded. The second event recorded is a NIM Download Event 706. TheEvent Log Module 98 preferably tracks the NIM ID 756, the provider ID750, the start time 752, and the end time 754 for this event. The nextthing a user may do is open the NIM (step 810). This consists ofretrieving the NIM definition from the user's User Profile and gettingNIM content from the provider 82, as discussed above. The NIM isdisplayed for the user and the Event Log Module 98 records a NIM DisplayEvent 708. However, at this point, the Event Log Module 98 can onlyrecord the start time 752, and the NIM ID 756 for this event. The endtime 754 is recorded when the NIM is closed.

For every page of content a user views within a NIM 812, a Page-ViewEvent 712 is recorded. Some page views may require content from theprovider 82. The NIM ID 756, and the start time 752 are recorded forthis event.

The NIM may also enable the user to click on a link that results innavigating to a full screen web browser (step 814). When a user doesthis, a Web Click-Through Event 710 is recorded. The Event Log Module 98records the NIM ID 756, the start time 752, and the URL of the web sitethat is passed from the NIM content to the browser 758.

When the NIM closes (step 816), the end time 754 for the NIM DisplayEvent 708 is recorded. When the user logs out of the home NIM (step818), the event log is uploaded to the Server 50 (of FIG. 1).

In one embodiment of the invention, the previously described Event LogModule 98 (within the client computer 20 of FIG. 1) tracks user eventsin the home NIM user application and uploads the information to theStatistics Database 80 (of the server computer 50 of FIG. 1) atpredetermined intervals alternate embodiments, the Event Log 700 (inFIG. 32) may be processed by the NIM Server before it is stored in theStatistics Database 80. For example, the NIM Server may process NIM usestatus information for each user that is currently logged in.

The Statistics Database 80, illustrated in FIG. 34, preferably listsevery event 1002 by every user of home NIMs along with the correspondingfields associated with each event. For-example, if a NIM Display Eventis recorded, the User ID 1004 of the user that performed the event islisted, the start time 1006 is listed, the end time 1008 is listed, andthe NIM ID 1010 is listed. If a Web Click-Through Event is recorded, theUser ID 1004 is listed, the NIM ID 1010 is listed, the start time 1006is listed, and the URL of the web site 1014 is listed. The StatisticsDatabase 80 therefore allows the list of events to be easily referencedand searched by each event or by each of the fields associated with theevents.

Referring to FIG. 35, the Statistical Analysis Module 900 uses theStatistics Database 80 in order to provide various services for thecontent provider partners 82. Preferably, the Statistical AnalysisModule 900 includes a Multi-Dimensional Consumer Profile Module 902, aReal-Time Advertising Module 904, and a Pack Building Module 906, asdiscussed below.

A primary advantage of the present invention is that, because NIMs areused in groups and are used more often and for longer periods of timethan web pages or web sites, real-time multi-dimensional NIM use data(that's a function of which NIMs are activated simultaneously) can beaccumulated. In accordance with an embodiment of the invention, thisaccumulated data is used to generate a multi-dimensional consumerprofiling database. The Multi-Dimensional Consumer Profile Module 902uses information from the Statistics Database 80 to examine, for eachuser, the start time, and the end time of each NIM Display Event It thendetermines the NIMs (using the NIM IDs) that are opened simultaneouslyfor each user. The Module 902 determines, for every selected NIM, theother NIMs that a given user may use in conjunction with the selectedNIM. The Module 902 also determines how often these other NIMs are usedsimultaneously with the selected NIM. For example, Company X provides aNIM for selling its books. The Multi-Dimensional Consumer Profile Module902 determines for Company X that a particular user has a NIM related tofinance activated 30% of the time the user has the book-selling NIMacted, a NIM related to computers 20% of the time the user has thebook-selling NIM activated, and a NIM related to wedding gifts 5% of thetime the user has the book-selling NIM activated. This will provideCompany X with a more complete profile of the user's interests.

The Real-Time Advertising Module 904 determines the NIMs that each userhas displayed at any given moment. This information is used by a contentprovider partner or by the NIM Server to target advertising information.For example, if a user has a NIM related to sports displayedsimultaneously with Company X's book-selling NIM, Company X uses thisinformation to stream an advertisement for a sports book. In oneembodiment, this is accomplished by associating each NIM with a contextkeyword. This is done by incorporating the context keyword into the NIMdefinition or, alternatively, by maintaining a table of NIMs and theircorresponding context keywords. For example, the NIM related to sportsis associated with the context keyword “sports.” Moreover, the Real-TimeAdvertising Module 904 may combine the real-time user information withthe historical user information from the Statistics Database 80 toprovide advertisers with a complete picture of a user's interests.

The Pack Building Module 906 uses the Statistics Database 80 todetermine which NIMs are being used simultaneously. The Module 906 alsodetermines which NIMs are being shared as NIM Packs. From this, theModule 906 provides information to content provider partners about whichNIMs should be bundled together. In alternate embodiments, the Module906 builds a NIM Pack based upon the information it processes. Forexample, if the Pack Building Module 906 determines that an airline NIMis being used with a hotel NIM and a car rental NIM, the Module 906 maybuild a NIM Pack with a restaurant NIM.

Additionally, in one embodiment of the present invention, the NIM Server82 may track the content within a NIM in a Content Database 1050, asillustrated in FIG. 36. A content descriptor 1052 which may be a stringdescribing the content that is shown within the NIM is recorded forcontent shown in the NIM. For example, if a NIM displayed anadvertisement for an automobile followed by an advertisement for arestaurant, the two recorded content descriptors might say “automobilead” and “restaurant ad.” In addition, the NIM ID 1054, the start time atwhich the content is displayed 1056, and the end time 1058 are allpreferably recorded for each content descriptor.

Referring to FIG. 35, The Content Analysis Module 950 is able tocorrelate, at any moment, the content displayed to the user as recordedin the Content Database with the user's NIM activity recorded in theStatistics Database. For example, if one NIM displays to a user anadvertisement for a travel book, the user may open a NIM related toFlorida, a NIM owned by a specific airline, and a NIM owned by a carrental company. This pattern of user behavior will allow the companythat provides the travel book advertisement to better understand theeffect of the advertisement on the user. The company may use thisinformation to make cross-promotions with other NIM providers, or,simply to provide more effective targeted advertisements.

In an alternative embodiment, each of the content providers may trackits own content information. The content providers could then compareits content information with the user information provided by theStatistics Database of the NIMServer.

Finally, referring to FIG. 37, all of the user event information may beused in conjunction with user information provided at login. During thelogin process, the user may be required to enter demographic informationsuch as age, marital status, etc. In one embodiment, this information isstored in a User Account Database 1100. Each User ID 1102 is listedalong with the corresponding user information 1104. Therefore, it ispossible to match the user events with personal information about theparticular user to give advertisers or NIM content providers a morecomplete behavior profile of each user.

The foregoing description, for purposes of explanation, used specificnomenclature to provide a thorough understanding of the invention.However, it will be apparent to one skilled in the art that the specificdetails are not required in order to practice the invention. In otherinstances, well known circuits and devices are shown in block diagramform in order to avoid unnecessary distraction from the underlyinginvention. Thus, the foregoing descriptions of specific embodiments ofthe present invention are presented for purposes of illustration anddescription. They are not intended to be exhaustive or to limit theinvention to the precise forms disclosed, obviously many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best utilize the invention andvarious embodiments with various modifications as are suited to theparticular use contemplated. It is intended that the scope of theinvention be defined by the following claims and their equivalents.

What is claimed is:
 1. A client computing device configured to access content over a network, the client computing device comprising: electronic storage configured to store networked information monitor template associated with a networked information monitor, the networked information monitor template having therein a definition of a viewer graphical user interface having a frame within which time-varying content in a web browser-readable language may be presented on a display associated with the client computing device, wherein the frame of the viewer graphical user interface lacks controls for enabling a user to specify a network location at which content for the networked information monitor is available; and one or more processors configured to execute one or more computer program modules, the one or more computer program modules being configured to access the networked information monitor defined by the networked information monitor template, wherein accessing the networked information monitor defined by the networked information monitor template results in: transmission, over a network to a web server at a network location, of a content request for content to be displayed within the frame of the viewer graphical user interface defined by the networked information monitor template; reception, over the network from the web server at the network location, of content transmitted from the web server in response to the content request, the content being time-varying; presentation, on the display, of the viewer graphical user interface defined by the networked information monitor template outside of and separate from any graphical user interface of any other application; and presentation, on the display within the frame of the viewer graphical user interface defined by the networked information monitor, of the time-varying content received from the web server.
 2. The method of claim 1, further comprising, responsive to reception of one or more elements included in the received time-varying content, modifying a feature of said viewer graphical user interface defined by the networked information monitor template in accordance with a modification corresponding to the received one or more elements.
 3. The client computing device of claim 2, wherein said modification corresponding to the received one or more elements comprises a modification to an image defined by the networked information monitor template as forming a part of said viewer graphical user interface.
 4. The client computing device of claim 2, wherein the correspondence between the modification and the received one or more elements is defined by the networked information monitor template.
 5. The client computing device of claim 2, wherein the one or more computer program modules and the networked information monitor template are configured such that modifying the feature of the viewer graphical user interface comprises adjusting a size of the frame of the viewer graphical user interface.
 6. The client computing device of claim 2, wherein the one or more computer program modules and the networked information monitor template are configured such that modifying the feature of the viewer graphical user interface comprises changing a color of a frame border or background of the viewer graphical user interface.
 7. The client computing device of claim 2, wherein the one or more computer program modules and the networked information monitor template are configured such that modifying the feature of the viewer graphical user interface comprises modifying text of the viewer graphical user interface in a manner defined by the networked information monitor template.
 8. The client computing device of claim 1, wherein the networked information monitor template includes a markup language file.
 9. The client computing device of claim 1, wherein one or more computer program modules are configured such that the time-varying content is received from the web server over the network according to the TCP/IP protocol.
 10. The client computing device of claim 1, wherein the network location corresponds to a uniform resource locator included in the networked information monitor template.
 11. The client computing device of claim 10, wherein the one or more computer program modules are further configured such that accessing the networked information monitor defined by the networked information monitor template results in transmission of the content request to the uniform resource locator included in the networked information monitor template, and the content request being transmitted according to the TCP/IP protocol over the network.
 12. The client computing device of claim 1, wherein the one or more computer program modules are further configured: to transmit, over the network to a networked information monitor server, a request for the networked information monitor template; to receive, from the networked information monitor server over the network, the networked information monitor template; and to store the networked information monitor template to the electronic storage.
 13. A computer-implemented method of accessing content over a network on a client computing device, the client computing device having electronic storage and one or more processors configured to execute one or more computer program modules, the client method comprising: storing, to the electronic storage, a networked information monitor template associated with a networked information monitor, the networked information monitor template having therein a definition of a viewer graphical user interface having a frame within which time-varying content in a web browser-readable language may be presented on a display associated with the client computing device, wherein the frame of the viewer graphical user interface lacks controls for enabling a user to specify a network location at which content for the networked information monitor is available; accessing the networked information monitor defined by the networked information monitor template, wherein accessing the networked information monitor defined by the networked information monitor template results in: transmission, over a network to a web server at a network location, of a content request for content to be displayed in the viewer graphical user interface defined by the networked information monitor template; reception, over the network from the web server at the network location, of content transmitted from the web server in response to the content request, the content being time-varying; presentation, on the display, of the viewer graphical user interface defined by the application media package template outside of and separate from any graphical user interface of any other application; and presentation, on the display within the frame of the viewer graphical user interface defined by the networked information monitor, of the time-varying content received from the web server.
 14. The method of claim 13, responsive to reception of one or more elements included in the received time-varying content, modifying a feature of said viewer graphical user interface defined by the networked information monitor template in accordance with a modification corresponding to the received one or more elements.
 15. The method of claim 14, wherein said modification corresponding to the received one or more elements comprises a modification to an image defined by the networked information monitor template as forming a part of said viewer graphical user interface.
 16. The method of claim 14, wherein the correspondence between the modification and the received one or more elements is defined by the networked information monitor template.
 17. The method of claim 14, wherein modifying the feature of the viewer graphical user interface comprises adjusting a size of the frame of the viewer graphical user interface.
 18. The method of claim 14, wherein modifying the feature of the viewer graphical user interface comprises changing a color of a frame border or background of the viewer graphical user interface.
 19. The method of claim 14, wherein modifying the feature of the viewer graphical user interface comprises modifying text of the viewer graphical user interface in a manner defined by the networked information monitor template.
 20. The method of claim 13, wherein the networked information monitor template includes a markup language file, and wherein storing the networked information monitor template comprises storing the markup language file.
 21. The method of claim 13, wherein the time-varying content is received from the web server over the network according to the TCP/IP protocol.
 22. The method of claim 13, wherein the network location corresponds to a uniform resource locator included in the networked information monitor template.
 23. The method of claim 22, wherein accessing the networked information monitor defined by the networked information monitor template results in transmission of the content request to the uniform resource locator included in the networked information monitor template, and the content request being transmitted according to the TCP/IP protocol over the network.
 24. The method of claim 13, further comprising: prior to storing the networked information monitor template to the electronic storage, transmitting, over the network to a networked information monitor server, a request for the networked information monitor template; and receiving, from the networked information monitor server over the network, the networked information monitor template. 